Red Hat Bugzilla – Bug 147502
GATEWAYDEV not evaluated properly when using two eth's as dhcp clients
Last modified: 2010-04-06 09:20:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
we have two interfaces eth0 and eth1 which are both configured via
dhcp and are getting both a default gw via dhcp.
It would be nice if GATEWAYDEV from /etc/sysconfig/network would be
As it is right now the default-gw from eth0 is always chosen.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: default route is chosen from the dhcp config sent by eth0
Expected Results: evaluation of GATEWAYDEV /etc/sysconfig/network
so if I set GATEWAYDEV=eth1 I would expect that the default route send
via dhcp on eth1 would be chosen.
happens on Fedora Core 3 as well
Does the patch in 133575 work for you?
Unfortunately not. It only applies to BOOTPROTO=static and not to the
I do believe all the gateway setting is done in dhclient-script.
This problem will be fixed in the next DHCP version.
If GATEWAYDEV is set, and the interface being configured with DHCP
is not the GATEWAYDEV, then the default route will not be created
by the dhclient-script .
The new dhclient-script also deletes any current default route before
attempting to create a new one; the reason eth0's DHCP router option
was always used as the default was that eth1's dhclient-script
session tried to create the default route, but it failed because
a default route already existed . For this reason, if GATEWAY is
set in /etc/sysconfig/network then no invocation of the new
dhclient-script should attempt to create a default route.
This fix will be in dhcp-3.0.1-11_EL3 shortly - I'll update this
bug when it is.
This bug is now fixed in dhcp-3.0.1-33_EL3, which is making its way
through QA and hopefully into RHEL-3-U5 . Meanwhile, you can download
Please test and let me know if it is OK or you have any problems.
Thanks, Jason Vas Dias, Red Hat .
ok. now the behaviour is as follows:
both interfaces get their ips and a default gw via dhcp.
If GATEWAYDEV is set the default route is always set according to the
GATEWAYDEV (which is what we/most people will want).
If there is no GATEWAYDEV it seems that the default gateway of the
last (eth1) interface will be used. Whether it is always the last or
only the interface which gets quicker a dhcp response I have not
verified. But since there is nowhere a preference this behaviour
should be ok.
Yes, the previous behavior was that ONLY the first DHCP session to
set the default gateway could succeed; if you happened to want the
second session to succeed, you'd be out of luck. Now at least one
has some control over this with GATEWAYDEV.
Interface devices are always brought up in the numerical order of
their interface number : eth0, eth1... etc. - and no interface
configuration begins before the previous session ends . While
dhclient is capable of configuring multiple interfaces in parallel,
this feature is not used .
This bug is fixed with dhcp-3.0.1-40_EL3+
Closing as WONTFIX. dhcp-3.0.1-10_EL3 is the latest version shipped for RHEL-3.