wpa_supplicant on bonding slave

Brian J. Murrell brian at interlinx.bc.ca
Fri Feb 6 13:33:35 EST 2009

On Tue, 03 Feb 2009 13:53:30 +0200, Jouni Malinen wrote:

> Do you tell wpa_supplicant about the bonding device? I think that
> bonding behaves similarly to bridging in the sense that the EAPOL frame
> reception needs special handling and you will likely need to add
> -b<bridge/bond ifname> to the wpa_supplicant command line.

OK.  Did that.
> Another potential problem is in which MAC address is actually used on
> the bonded device. IEEE 802.11 does not allow client mode to transmit
> using any other MAC address than the address of the card itself. In
> other words you will need to make sure that the wireless interface MAC
> address gets selected one way or another. I've never tested Linux
> bonding, so I do not know what kind of tricks this may need.

Fixed that too.  Now it looks like:

bond0     Link encap:Ethernet  HWaddr 00:0e:35:eb:cf:e1  
          inet addr:  Bcast:  Mask:
          inet6 addr: 2001:4978:161:0:20e:35ff:feeb:cfe1/64 Scope:Global
          inet6 addr: fe80::20e:35ff:feeb:cfe1/64 Scope:Link
          RX packets:19377 errors:11823 dropped:12442 overruns:0 frame:0
          TX packets:3450 errors:0 dropped:0 overruns:0 carrier:3450
          collisions:0 txqueuelen:0 
          RX bytes:4291142 (4.0 MB)  TX bytes:741685 (724.3 KB)

eth0      Link encap:Ethernet  HWaddr 00:0e:35:eb:cf:e1  
          RX packets:19371 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3449 errors:0 dropped:0 overruns:0 carrier:3449
          collisions:0 txqueuelen:1000 
          RX bytes:2309578 (2.2 MB)  TX bytes:669748 (654.0 KB)
          Interrupt:11 Base address:0xcc00 

eth2      Link encap:Ethernet  HWaddr 00:0e:35:eb:cf:e1  
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:11823 dropped:12442 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000 
          RX bytes:1981564 (1.8 MB)  TX bytes:71937 (70.2 KB)
          Interrupt:5 Base address:0xe000 Memory:f8ffe000-f8ffefff 

eth0 is the wired and eth2 the wireless interface.

> You should use wpa_supplicant debug output from stdout (start it
> manually with -dd on command line) to get all debug messages.

OK.  I tried to send that here.  Got moderated due to file size.  The log 
can be found at: http://brian.interlinx.bc.ca/wpa_supplicant.debug



More information about the HostAP mailing list