https://bugzilla.novell.com/show_bug.cgi?id=821077 https://bugzilla.novell.com/show_bug.cgi?id=821077#c3 --- Comment #3 from Marius Tomaschewski 2013-05-23 06:44:49 UTC --- I think we should fix this cosmetic issue, because it may confuse people, that route (and of course also a "netstat -r") shows "default" already for the 0.0.0.0 destination network address without to consider the mask: Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 nic0 0.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 nic0 0.0.0.0 0.0.0.0 192.0.0.0 U 0 0 0 nic0 0.0.0.0 0.0.0.0 128.0.0.0 U 0 0 0 nic0 0.0.0.0 x.x.x.x 0.0.0.0 UG 0 0 0 nic0 Destination Gateway Genmask Flags MSS Window irtt Iface default * 255.0.0.0 U 0 0 0 nic0 default * 240.0.0.0 U 0 0 0 nic0 default * 192.0.0.0 U 0 0 0 nic0 default * 128.0.0.0 U 0 0 0 nic0 default edge-20 0.0.0.0 UG 0 0 0 nic0 For completeness, "ip route" shows them correctly: 0.0.0.0/8 dev nic0 scope link 0.0.0.0/4 dev nic0 scope link 0.0.0.0/2 dev nic0 scope link 0.0.0.0/1 dev nic0 scope link default via x.x.x.x dev nic0 BTW: More funny is: # route -n 172.42.40.0 0.0.0.0 255.255.255.0 U 0 0 0 nic0 # route default * 255.255.255.0 U 0 0 0 nic0 # grep ^default /etc/networks default 172.42.40.0 => IMO low prio minor. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=821077 https://bugzilla.novell.com/show_bug.cgi?id=821077#c5 --- Comment #5 from Bernd Eckenfels 2013-08-30 12:08:13 UTC --- (this does not skip the lookup of networks [BTW in Comment #3], therefore if you have a broken /etc/networks entry it will (still) show a broken output for ipv4 - how would you fix it?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=821077 https://bugzilla.novell.com/show_bug.cgi?id=821077#c7 --- Comment #7 from Marius Tomaschewski 2013-08-30 13:33:56 UTC --- (In reply to comment #4)

This is fixed here (you might need to pull other changes as well to apply that change):

https://github.com/ecki/net-tools/commit/c0d46405eb1d58bb5e2e2f5555a05fe10db...

Thank you very much!! (In reply to comment #5)

(this does not skip the lookup of networks [BTW in Comment #3], therefore if you have a broken /etc/networks entry it will (still) show a broken output for ipv4 - how would you fix it?)

I'd keep it as is. A broken /etc/networks entry is a broken entry, IMO no fix is needed. Except of it, /etc/networks assumes class networks, there is no length. The man page we have says: This file is read by the route(8) and netstat(8) utilities. Only Class A, B or C networks are supported, partitioned networks (i.e., network/26 or network/28) are not supported by this facility. 0.0.0.0 is a class A and partitioned networks (0.0.0.0/4) are not supported. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.