Bug 437576 - flushes routing table on restart
flushes routing table on restart
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: wpa_supplicant (Show other bugs)
8
powerpc Linux
low Severity low
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-14 18:52 EDT by Ian Chapman
Modified: 2008-03-17 16:23 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-17 16:23:17 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)
Contents of /etc/sysconfig/wpa_supplicant (57 bytes, text/plain)
2008-03-14 18:52 EDT, Ian Chapman
no flags Details
Contents of /etc/wpa_supplicant/wpa_supplicant.conf (151 bytes, text/plain)
2008-03-14 18:53 EDT, Ian Chapman
no flags Details
Log file (using -dd option) during a network restart followed by wpa_supplicant restart (16.27 KB, text/plain)
2008-03-14 18:59 EDT, Ian Chapman
no flags Details

  None (edit)
Description Ian Chapman 2008-03-14 18:52:25 EDT
Description of problem:

When restarting wpa_supplicant is restarted, the routing table is flushed,
leaving nothing but the interface IP, ie the default gateway is missing.

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

wpa_supplicant-0.5.7-21.fc8.ppc
wireless-tools-29-0.2.pre22.fc8.ppc
kernel-2.6.24.3-12.fc8.ppc

How reproducible:

I'm using a Powerbook G4, with Broadcom BCM4306 (rev 03) wireless chipset and
the b43 driver. The card connects and works with my AP without any major
hassles, however if I ever need to restart my network for whatever reason, I
have the following problem.

1. Restarting the network "breaks" the connection to the AP (fair enough...)
2. Restarting wpa_supplicant restores the connection to the AP, but leaves me
with an (almost) empty routing table.
3. Restarting the network again, restores the routing table but of course breaks
the connection to the AP again.


Steps to Reproduce:
1. service network restart
2. service wpa_supplicant restart
3.
  
Actual results:

I'm able to restore connection to the AP, but with empty routing tables.


Expected results:

Routing tables shouldn't be empty and access to the AP should be restored.

Additional info:

Routing table before restart:

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 wlan0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 wlan0
0.0.0.0         192.168.1.254   0.0.0.0         UG    0      0        0 wlan0


After restart:

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 wlan0

Also, see attachments:
Comment 1 Ian Chapman 2008-03-14 18:52:25 EDT
Created attachment 298100 [details]
Contents of /etc/sysconfig/wpa_supplicant
Comment 2 Ian Chapman 2008-03-14 18:53:38 EDT
Created attachment 298101 [details]
Contents of /etc/wpa_supplicant/wpa_supplicant.conf
Comment 3 Ian Chapman 2008-03-14 18:59:12 EDT
Created attachment 298102 [details]
Log file (using -dd option) during a network restart followed by wpa_supplicant restart
Comment 4 Ian Chapman 2008-03-14 19:02:18 EDT
I should probably list the following too:

ONBOOT=yes
USERCTL=no
IPV6INIT=no
PEERDNS=no
TYPE=Wireless
DEVICE=wlan0
HWADDR=00:0d:93:ea:fd:eb
BOOTPROTO=none
NETMASK=255.255.255.0
DHCP_HOSTNAME=
IPADDR=192.168.1.30
DOMAIN=
ESSID=atmosphere
CHANNEL=11
MODE=Managed
RATE=36M
Comment 5 Dan Williams 2008-03-17 16:23:17 EDT
The supplicant doesn't do any routing table manipulation; after a restart of the
supplicant you'll definitely need to 'ifup wlan0' if you want to get the routes
and address back.

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