https://bugzilla.novell.com/show_bug.cgi?id=480922 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=480922#c10 --- Comment #10 from Marius Tomaschewski <mt@novell.com> 2009-03-06 05:13:11 MST --- (In reply to comment #9)
I see! Thanks for the explanation.
I still have one issue, though - I would still expect that the standard network setup tools work as expected and I have full manual control when /etc/init.d/network is stopped.
They're just integrated to use the system policies.
I believe the current behavior is confusing for experienced admins/hackers.
How common is it to have dhclient legitimely not set a default route?
Very common; always when you've more than one interface using dhcp.
I believe the solution might simply be to add:
if [ "$DHCLIENT_SET_DEFAULT_ROUTE" = yes ] ; then ... else echo "Warning: Not being told by NetworkManager to set up default route" >&2 fi
NetworkManager is not using /sbin/dhclient-script but an own script ;-) This default script is used by ifup.
This explains to people running dhclient manually that it is not setting up default route intentionally, gives them a string to grep for to find out where this decision happens, and lets them override the check suitably.
Well, it would be possible to log a warning or even to add a check if the network or NetworkManager is running and if there is a ifcfg file. When not, just set the default route then. Question is then, what to with the other things that the script is doing, especially with the resolv.conf. Hmm... I don't know - you are requesting a fix for an unsupported setup that is not using NetworkManaher or ifup but your own scripts. -- 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.