Bug 163062 - Default route not set for ath0 device after upgrade to Fedora Core 4
Default route not set for ath0 device after upgrade to Fedora Core 4
Status: CLOSED DUPLICATE of bug 149780
Product: Fedora
Classification: Fedora
Component: system-config-network (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-12 14:01 EDT by David Anderson
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-19 06:31:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Anderson 2005-07-12 14:01:32 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4) KHTML/3.4.1 (like Gecko)

Description of problem:
I have a Dell Inspiron laptop, with a Netgear wireless PCMCIA card, that has 
an Atheros chipset (Madwifi driver). 
 
Today I upgraded this machine from Fedora Core 2 to Fedora Core 4. 
 
Everything still works fine, networking-wise, except that when the ath0 
interface is brought up, the default route is not set: 
 
[root@shed network-scripts]# /sbin/route -n 
Kernel IP routing table 
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface 
[root@shed network-scripts]# /sbin/ifup ath0 
 
Determining IP information for ath0... done. 
[root@shed network-scripts]# /sbin/route -n 
Kernel IP routing table 
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface 
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 ath0 
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 ath0 
 
The ath0 device is configured for DHCP. Here is the DHCP lease: 
 
[root@shed network-scripts]# cat /var/lib/dhcp/dhclient-ath0.leases 
lease { 
  interface "ath0"; 
  fixed-address 192.168.1.3; 
  option subnet-mask 255.255.255.0; 
  option routers 192.168.1.1; 
  option dhcp-lease-time 259200; 
  option dhcp-message-type 5; 
  option domain-name-servers 192.168.1.1; 
  option dhcp-server-identifier 192.168.1.1; 
  renew 4 2005/7/14 02:04:09; 
  rebind 5 2005/7/15 08:58:08; 
  expire 5 2005/7/15 17:58:08; 
} 
 
Here is my ifcfg-ath0, (which as you can see has some settings left over from 
a static IP assignment): 
 
[root@shed network-scripts]# cat ifcfg-ath0 
DEVICE=ath0 
BOOTPROTO=dhcp 
WIRELESS=yes 
HOTPLUG=yes 
MODE=Managed 
ESSID=((REMOVED)) 
IPV6INIT=no 
ONBOOT=no 
USERCTL=yes 
PEERDNS=yes 
NETMASK=255.255.255.0 
DHCP_HOSTNAME=shed 
IPADDR=192.168.100.3 
DOMAIN= 
HWADDR=00:09:5b:c7:48:3b 
GATEWAY=192.168.100.1 
TYPE=Wireless 
RATE=Auto 
CHANNEL=11 
 
This problem doesn't happen with the eth0 interface - it's specific to the 
wireless interface. 

Version-Release number of selected component (if applicable):
8.11.1-1

How reproducible:
Always

Steps to Reproduce:
1. /sbin/ifup ath0 
   

Actual Results:  IP address obtained, default route not set. 

Expected Results:  Default route set. 

Additional info:
Comment 1 Bill Nottingham 2005-07-12 14:40:08 EDT
What happens if you take the GATEWAY= line out?
Comment 2 David Anderson 2005-07-12 17:07:49 EDT
Yup, that fixes it.  
  
However, if I use system-config-network to switch to using a static IP 
address, and then switch back again to using DHCP, then the line is back (and 
hence the default route from DHCP is not used, which means I get no default 
route). 
 
Worked in FC2, so one of the changes in the meantime will be the cause. 
 
Comment 3 Bill Nottingham 2005-07-12 17:27:30 EDT
I believe the dhclient script was fixed to not set a gateway route if one was
specified; with it in the config file, it appears that one is.

Perhaps s-c-network should take the line out when you switch to a dynamic config?
Comment 4 David Anderson 2005-07-12 17:38:24 EDT
"Perhaps s-c-network should take the line out when you switch to a dynamic  
config?" - I think you're about right. If you switch in s-c-n to "obtain IP 
settings from DHCP" then it ought to mean just that and not "but retain the 
gateway from your previous static IP settings even though they're greyed-out 
and in a different part of the dialogue box".  
However, if you drop the GATEWAY= line then it has to be manually remembered 
and re-entered by the user when he switches back to static settings. (At 
present it's still in there and in s-c-n it's greyed-out in the static IP 
settings part of the dialogue). It would be inconsistent for s-c-n to 
automatically remember two of the static IP settings but not the third.  
  
Comment 5 David Anderson 2005-07-12 17:50:56 EDT
Or perhaps the change in dhclient should be reversed? Or a different parameter 
used for overriding the DHCP-supplied gateway, e.g. DHCP_STATIC_GATEWAY=  or 
OVERRIDE_GATEWAY=YES ?? 
Comment 6 David Anderson 2005-07-13 17:17:11 EDT
This bug appears to be a duplicate of 149780, and the bug is really in s-c-n 
for making a setting that it shouldn't... 
Comment 7 David Anderson 2005-07-13 17:18:47 EDT
Having said that though (#6), the bug can't be fixed just by fixing future 
versions of s-c-n, because there will be people, like me, upgrading from 
previous versions of Fedora Core that have DHCP and GATEWAY=. As the version 
of s-c-n in FC4 still sets BOTH of these, it'll be happenning for a long time 
to come still (e.g. people upgrading from FC4 to FC5 or FC6...). 
Comment 8 Harald Hoyer 2006-05-19 06:31:14 EDT

*** This bug has been marked as a duplicate of 149780 ***

Note You need to log in before you can comment on or make changes to this bug.