Hi, On Wed, May 15, 2019 at 9:34 PM Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Wed, 2019-05-15 at 16:40 -0400, Alex wrote: > > The problem is that, after bringing it back to his house and putting > > it online, the default route was not added properly and the system > > was unreachable until I stepped him through the process of adding it > > manually. > > > > This is the command I had him run as root to configure the default > > route: > > > > # route add default gw 192.168.9.1 dev enp4s6 > > > > Here is that /etc/sysconfig/network-scripts/ifcfg-Wired_connection_2 > > config: > > > > HWADDR=00:0E:0C:3B:35:68 > > TYPE=Ethernet > > PROXY_METHOD=none > > BROWSER_ONLY=no > > BOOTPROTO=none > > IPADDR=192.168.9.110 > > PREFIX=24 > > GATEWAY=192.168.9.1 > > DEFROUTE=yes > > IPV4_FAILURE_FATAL=no > > IPV6INIT=yes > > IPV6_AUTOCONF=yes > > IPV6_DEFROUTE=yes > > IPV6_FAILURE_FATAL=no > > IPV6_ADDR_GEN_MODE=stable-privacy > > NAME="Wired connection 2" > > UUID=850cde8f-7dc2-364a-8911-e511cdbea2e4 > > ONBOOT=yes > > DNS1=8.8.4.4 > > AUTOCONNECT_PRIORITY=-999 > > > > Is there something immediately identifiable that would prevent the > > default route from working? > > > > Typically NAME and DEVICE are the name of the device, like enp4s6, > > but they don't exist in this config. Is that what is missing? I can't > > easily reboot this machine, so want to be sure before I do it. > > Things that spring to mind are: > > Is his gateway using the same numerical IP as when you got it working > on your network? Yes. > You're using manual configuration, instead of DHCP. Does his LAN have > a DHCP server that would have automatically managed this all for him? I'm doing port forwarding from the cable modem to his IP, so while most of the network uses DHCP, I've set his computer to use a static address to be able to forward http and ssh to his machine. > Was his gateway up and running before the computer booted up? (I'm > unsure if an unavailable gateway would have been removed from pre- > configured settings, though.) Before it booted up? I'm not sure I understand. I couldn't reach his computer prior to him typing the route command I've shown above. After having added it, I could successfully connect to it remotely. There are a few NetworkManager messages printed during boot, but not sure they indicate any problems: May 15 08:39:50 localhost NetworkManager[796]: <warn> [1557923990.7338] acd[0x56313c844a30,3]: couldn't init ACD for announcing addresses on interface 'enp4s6': Operation not permitted May 15 08:39:50 localhost NetworkManager[796]: <info> [1557923990.7341] device (enp4s6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') May 15 08:39:50 localhost NetworkManager[796]: <info> [1557923990.7377] device (enp4s6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') May 15 08:39:50 localhost NetworkManager[796]: <info> [1557923990.7385] device (enp4s6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') May 15 08:39:50 localhost NetworkManager[796]: <info> [1557923990.9552] policy: set 'Wired connection 2' (enp4s6) as default for IPv4 routing and DNS May 15 08:39:50 localhost NetworkManager[796]: <info> [1557923990.9561] device (enp4s6): Activation: successful, device activated. May 15 08:39:50 localhost nm-dispatcher[876]: req:2 'up' [enp4s6]: new request (3 scripts) May 15 08:39:50 localhost nm-dispatcher[876]: req:2 'up' [enp4s6]: start running ordered scripts... I think worse case I'll set NAME= and DEVICE= in the config, and also set some type of cron job or shell script that manually adds the route as root after some period of time, to give me some time to access the machine in case modifying the config doesn't work. Thanks, Alex _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
