On 5/16/19 4:40 AM, Alex wrote:
Hi,
I've just installed fedora30 desktop on a friend's computer for him.
It was installed and configured here before he brought it to his house
and connected it to his cable modem. Previously I had set up port
forwarding on his modem from port 8027 to port 8027 on his system for
web access and port 8022 to port 8022 on his system for remote ssh
access.
I used the gnome network manager to configure networking and just
manually configured ssh to listen on port 8022 instead of the default.
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.
It would be best too know the conditions "before" and "after" the
manual addition of the
route. If it is working with the above it is hard to determine why it didn't work
prior.
--
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme