Bug 147502
Summary: | GATEWAYDEV not evaluated properly when using two eth's as dhcp clients | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Moritz Baumann <baumanmo> |
Component: | dhcp | Assignee: | Jiri Popelka <jpopelka> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | benl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | RHEL3U7NAK | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-04-06 13:20:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 190430 |
Description
Moritz Baumann
2005-02-08 16:58:51 UTC
Does the patch in 133575 work for you? Unfortunately not. It only applies to BOOTPROTO=static and not to the dynamic section. 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 it from: http://people.redhat.com/~jvdias/DHCP/RHEL-3/ 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. |