Bug 6834

Summary:	wpa_supplicant does not work if wifi device is part of a bridge
Product:	Drivers	Reporter:	Tobias Diedrich (ranma+kernel)
Component:	network-wireless	Assignee:	John W. Linville (linville)
Status:	REJECTED INSUFFICIENT_DATA
Severity:	normal	CC:	alexandre.rossi, bunk, protasnb
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.17-rc6	Subsystem:
Regression:	---	Bisected commit-id:

Description Tobias Diedrich 2006-07-14 08:15:58 UTC

Most recent kernel where this bug did not occur:
Distribution: Debian unstable
Hardware Environment: Thinkpad R52
Software Environment: 
Problem Description: 

Normally my notebook can connect just fine to the AP using WPA with
wpa_supplicant.  However, to ease switching between LAN and wireless, I'd like
to use a bridge and add/remove the network device I'm using/not using.
This worked just fine with WEP, but with WPA wpa_supplicant would lose the
connection after adding the wifi device to the bridge (and can't establish the
connection for a wifi device already on the bridge).

Steps to reproduce:

Make sure WPA works.
Add wifi device to bridge and try again.

Comment 1 Adrian Bunk 2006-08-06 04:06:28 UTC


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

Comment 2 Adrian Bunk 2006-08-06 04:20:02 UTC

Sorry, this was a typo.

Comment 3 John W. Linville 2007-03-01 11:23:09 UTC

Does the MAC address of the bridge match the MAC address of the wireless 
device?

Comment 4 Anonymous Emailer 2007-03-05 09:32:59 UTC

Reply-To: ranma@tdiedrich.de

> ------- Additional Comments From linville@tuxdriver.com  2007-03-01 11:23 -------
> Does the MAC address of the bridge match the MAC address of the wireless 
> device?

Yes, this is reproducable with wlan0 as the only device in the
bridge, so the MAC addresses are the same. (I just checked to be
safe)

This is on 2.6.19 using the ipw2200 driver, steps to reproduce:

ifup wlan0 # Up the device wlan0 and start wpa_supplicant on it
# wlan0 is now associated, wpa_supplicant is running on device wlan0
brctl addbr br0
brctl addif br0 wlan0
# wait until reassociation is done or force one with 'disconnect' in wpa_cli
# reassociation fails

wpa_cli messages:

> disconnect
OK
> <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Trying to associate with 00:12:17:15:fe:9e (SSID='yamamaya' freq=0 MHz)
<2>Associated with 00:12:17:15:fe:9e
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Trying to associate with 00:12:17:15:fe:9e (SSID='yamamaya' freq=0 MHz)
<2>Associated with 00:12:17:15:fe:9e
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Trying to associate with 00:12:17:15:fe:9e (SSID='yamamaya' freq=0 MHz)
<2>Associated with 00:12:17:15:fe:9e
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Trying to associate with 00:12:17:15:fe:9e (SSID='yamamaya' freq=0 MHz)
<2>Associated with 00:12:17:15:fe:9e
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Trying to associate with 00:12:17:15:fe:9e (SSID='yamamaya' freq=0 MHz)
<2>Associated with 00:12:17:15:fe:9e
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Trying to associate with 00:12:17:15:fe:9e (SSID='yamamaya' freq=0 MHz)
<2>Associated with 00:12:17:15:fe:9e
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
[Now I remove wlan0 from the bridge with "brctl delif br0 wlan0"]
<2>Trying to associate with 00:12:17:15:fe:9e (SSID='yamamaya' freq=0 MHz)
<2>Associated with 00:12:17:15:fe:9e
<2>WPA: Key negotiation completed with 00:12:17:15:fe:9e [PTK=TKIP GTK=TKIP]
<2>CTRL-EVENT-CONNECTED - Connection to 00:12:17:15:fe:9e completed (reauth) [id=1 id_str=]

HTH,

Comment 5 Natalie Protasevich 2007-08-01 22:49:02 UTC

Any updates on this problem?
Thanks.

Comment 6 Adrian Bunk 2007-10-06 12:44:54 UTC

Please reopen this bug if it's still present with kernel 2.6.22.