Gateway gone (0.0.0.0) after reboot

Kernels & Hardware, configuring network, installing services

Gateway gone (0.0.0.0) after reboot

Postby JC_B » 2018-05-26 13:27

Hello Ladies and Gents,

I am a bit stumped, admittedly still a bit new to Debian/Linux, so I hope that I can get some direction on my issue. I have searched the web for several hours but not seeing a comfortable solution.

Issue :
After a reboot, I loose my default GW for the wired connection
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 UG 100 0 0 enp37s0

Now, if I navigate to the, what I believe is the network manager gui found in under Debian Stretch settings, simply turn off and back on the wired connection via the toggle, I will then get the gateway and I can access the Internet as expected.

I have also tested this with WiFi; however after a reboot, I will get the correct GW and can route past my LAN.

Configuration:
I have a static IP configured: This was performed with the network manager GUI IP, Mask and GW.... DNS is hard set

ifconfig: (Note: this is after off and on again via the previous stated method with the wired connection)
enp37s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.50.70 netmask 255.255.255.0 broadcast 192.168.50.255
inet6 fe80::7285:c2ff:fe5e:1e20 prefixlen 64 scopeid 0x20<link>
ether 70:85:c2:5e:1e:20 txqueuelen 1000 (Ethernet)
RX packets 162460 bytes 196891611 (187.7 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 122318 bytes 11377950 (10.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xf7500000-f751ffff


Some back story:
I have built a new PC, new MoBo and CPU, etc.... Same HDD as on the previous built and had no issues prior with same static configuration. I did need to 'perform some magic google searching' to get the new video card (GEFORE GT1030) and the Intel drivers for WiFi. The NIC worked out the box (but had same GW issue) but no WiFi until I loaded the drivers.

Sorry that this make it a bit of a mess, but I hope to learn quite a bit more with this issue. Preferably, I wish to continue to use the 'stock' network manager GUI and I really appreciate your time. Please request from me additional details that may need to help solve the issues, as well as teach me a lesson or two. As I like to say, you don't know, what you don't know :)

Thank you and best regards,

######################
##
## Fixed the issue ##
##
######################

Follow up:

I did manage to get this to work, but I am still a bit perplexed why it needed to be manually configured versus using the network manager. I edited /etc/network/interface and had to add in the routes are well for it to work as expected

#Ethernet
auto enp37s0
iface enp37s0 inet static
address 192.168.50.70
netmask 255.255.255.0
gateway 192.168.50.1
dns-nameservers 192.168.50.70
up route add -net 192.168.50.0 netmask 255.255.255.0 gw 192.168.50.1
up route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.50.1


Not sure if this was the best way to correct it or not, but wanted to add in these note in the event that there is a way to get this to work with network manager to if someone else is having this issue


JC
JC_B
 
Posts: 1
Joined: 2018-05-26 13:01

Return to System configuration

Who is online

Users browsing this forum: DarthSatan and 8 guests

fashionable