Hide Forgot
Description of problem: New dhclient doesn't set gateway properly. Version-Release number of selected component (if applicable): dhclient-3.0.1-40_FC3.x86_64.rpm How reproducible: If the connection to the internet is eth0, an ifcfg-eth0 script with a bad value for "GATEWAY=" will cause the value of gateway to be put into the routing table. Steps to Reproduce: 1. In ifcfg-eth0 enter ... BOOTPROTO=dhcp ... GATEWAY=192.168.10.1 ... 2. invoke ifup eth0 Actual results: # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 192.168.0.0 * 255.255.0.0 U 0 0 0 eth0 default 192.168.10.1 0.0.0.0 UG 0 0 0 eth0 Expected results: route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 192.168.0.0 * 255.255.0.0 U 0 0 0 eth0 default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 Additional info: This problem started when I "upgraded" from dhclient-3.0.1-30_FC3.x86_64.rpm to dhclient-3.0.1-40_FC3.x86_64.rpm
You've set GATEWAY to : GATEWAY=192.168.10.1 in ifcfg-eth0. With dhcp-3.0.1-40_FC3, the dhclient-script now correctly honors the GATEWAY and GATEWAYDEV settings. If the ip-address and subnet-mask received from DHCP are on the same subnet as the "$GATEWAY" setting, "$GATEWAY" becomes the gateway of the default route, which in your case is 192.168.10.1 . If you don't want dhclient-script to set the gateway to this value, remove or comment out the GATEWAY setting in ifcfg-eth0 . *** This bug has been marked as a duplicate of 149780 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.