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?
You're using manual configuration, instead of DHCP. Does his LAN have
a DHCP server that would have automatically managed this all for him?
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.)