What is a likely cause of missing default route?

English Network/Internet
#1

Turned on a linux box that has been off for a while and encountered an issue where my routing table did not have the default route anymore so although it could ping network machines it found external addresses unreachable. Route add fixed it as per http://superuser.com/questions/667631/network-is-unreachable-when-attempting-to-ping-google-but-internal-addresses

Any idea how this could go missing? Is this likely a network manager bug as suggested in the issue. Can I avoid using network manager on suse?

#2

Ah, now I notice it keeps losing it after each reboot! What could be causing this?

#3

Well, “route add” only affects the running system, it doesn’t save anything. So no wonder your changes get lost on reboot.
You can permanently set up your routes in YaST or NetworkManager, depending on what you use (wicked/ifup or NetworkManager).

That said, it shouldn’t be necessary.

Can you please at least tell what openSUSE version this is about? And maybe details about how you set up your network might help too (e.g. DHCP or static IP address, wired/wireless, …)

Regarding your question: yes, you can avoid using NetworkManager. Switch to ifup or wicked (13.2 and up) in YaST->Network Devices->Network Settings->Global Options.
You have to configure your network interfaces in YaST then, although the defaults should be ok normally.

#4

Can you realy not explain what “sort” of Linux. Is it openSUSE? When you do not know please try

cat /etc/os-release
#5

How did you determine you are missing a default route, only by the description you give(which is circumstantial) or actually inspecting your default route?
If you are running a relatively modern Linux (hopefully openSUSE) the following should display your working configuration

ip route

TSU

#6

openSUSE 12.3 (Dartmouth) (x86_64)

#7

Simply because the linked article said to try it and it works with it.

#8

Using YaST > Network Devices > Network Settings, you can use for Network manager or for ifup.

When you do not want to use NM, choose ifup.

Then it depends on using DHCP or not. When you use DHCP, the default router should be provided from the DHCP server (usualy your router/modem). When not, you must configure it yourself in the appropriate tabs.

PS. When we apparently like to know which version of openSUSE you use and offer prominent a menu where you can choose that and when then 12.3 (being an unsupported version) is not in the list, we hope that you understand the message that we like to see that first thing in your thread. So please, next time.

#9

Sorry, OK now it’s not working when I reboot and add the route either, haha .
It takes a takes a minute or so to output route as well is that ‘normal’

In YAST network settings it claims to be using ifconfig/ifup but I still occasionally see the network manager icon in the the system tray (or whatever it’s called on linux) is this right?

If ifconfig is known to be buggy in 12.3. What is actually the best way to upgrade from 12.3 to the latest?

#10

On 2015-08-13 20:46, moconnell wrote:

> If ifconfig is known to be buggy in 12.3. What is actually the best way
> to upgrade from 12.3 to the latest?

That’s not /the/ reason for upgrading.

For you, probably the best way is to install fresh the current version,
13.2.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#11

When it is on ifconfig inYaST it is on ifconfig. Do not let yourself become distracted from the rest of my post by seeing NM icon. Answer what I asked you. Do you use DHCP or not?

#12

Staticly assigned.

#13

Well, then enter the default route (and the other things like IP address, netmask, hostname, …) in the appropriate tabs and fields there… What is the problem?

#14

Now that you have hopefully configured your default route/gateway in YaST:

(From KDE) right-click on the System Tray, choose System Tray Settings, find the entry for Network Manager and deselect it or change its visibility from Auto to Never.

If ifconfig is known to be buggy in 12.3. What is actually the best way to upgrade from 12.3 to the latest?

I cannot remember ifconfig to be buggy in 12.3 – do you have any evidence?

#15

In YAST>Network Devices>Network Settings> Overview, I have statically assigned IPAddress: 192.168.1.100 Subnet: /24 hostname:Somename

I saved these again as I believe these ‘should’ work. ->
ip route:
127.0.0.0/8 dev lo scope link
169.254.0.0/16 dev eth0 scope link
192.168.1.0/24 dev eth0 proto kernel scope link src 192.1.100

ie still no 'default listed.
-> Still can’t even ping router on 192.168.1.254. Host unreachable.

INTERNET DID PREVIOUSLY WORK AFTER ADDING THE DEFAULT ROUTE IN KONSOLE AT LEAST TWICE BEFORE (THEN LOSING THE SETTING EITHER AFTER REBOOT OR AFTER SOME PERIOD OF TIME)

SO Using the YAST>Network Devices >Network Settings>Routing I manually added: Default IPv4 gateway 192.168.1.254 on Eth0, but NOT using the Routing table section to add anything (appears empty). I get the same ip route output with this extra line at the top:
default 192.168.1.254 dev eth0

->Still can’t even ping router. I had a working internet earlier when I did this from the cmd line with I think similar ifconfig output.

#16

Done (but of course this should be done for me as soon as YAST is set to not use it)…

I cannot remember ifconfig to be buggy in 12.3 – do you have any evidence?

I know that I have not changed the configuration for some time and the network now is non functional. I attribute this to bug in the software. It could be a bug in the hardware I suppose. The network configuration module seems a reasonable place to attribute blame or at least look for it, doesn’t it? Of course evidence is thin on the ground.:slight_smile:

#17

Just noticed I can ping other machines on the network just not the gateway?

#18

Rebooted the machine and the router to no avail. Any ideas welcome.

#19

We need to see what you see. Can you share the following info?

ip addr

ip route

Copy/paste output to a text file and transfer by memory stick if necessary

Same with configuration file (eg /etc/sysconfig/network/ifcfg-eth0) please.

#20

On 2015-08-14 00:06, moconnell wrote:
>
> hcvv;2723811 Wrote:
>> Well, then enter the default route (and the other things like IP
>> address, netmask, hostname, …) in the appropriate tabs and fields
>> there… What is the problem?
>
> In YAST>Network Devices>Network Settings> Overview, I have statically
> assigned IPAddress: 192.168.1.100 Subnet: /24 hostname:Somename

But you have not set the gateway.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))