#2136 NORM Trial-3: XO joining network causes openwrt AP to add wds interface

[Zarro Boogs per Child]

#2136: XO joining network causes openwrt AP to add wds interface
-----------------------+----------------------------------------------------
  Reporter:  sjoerd    |       Owner:  luisca                           
      Type:  defect    |      Status:  new                              
  Priority:  normal    |   Milestone:  Trial-3                          
 Component:  wireless  |     Version:  Development build as of this date
Resolution:            |    Keywords:                                   
  Verified:  0         |  
-----------------------+----------------------------------------------------
Comment (by Quozl):

 Reproduced this problem with OS Build 540 on B4 against an !OpenWrt access
 point.

 The output of ''ethtool'' on the B4 is as follows:

 {{{
 driver: libertas
 version: COMM-USB8388-322.p1-dbg
 firmware-version: 5.110.16.p1
 bus-info:
 }}}

 Before the B4 is associated, the access point does not list the WDS
 interface.  After the B4 is associated, the interface appears:

 {{{
 wds0.4915 Link encap:Ethernet  HWaddr 00:13:10:44:5F:AD
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 }}}

 Starting another B4 results in another WDS interface being created, with a
 different interface name.

 The !OpenWrt ''dmesg'' shows some transitions:

 {{{
 wds0.49153: attempt to add interface with same source address.
 br0: port 3(wds0.49153) entering learning state
 br0: port 3(wds0.49153) entering forwarding state
 br0: topology change detected, propagating
 br0: port 3(wds0.49153) entering disabled state
 br0: port 3(wds0.49153) entering disabled state
 device wds0.49153 left promiscuous mode
 device wds0.49153 entered promiscuous mode
 wds0.49153: attempt to add interface with same source address.
 br0: port 3(wds0.49153) entering learning state
 br0: port 3(wds0.49153) entering forwarding state
 br0: topology change detected, propagating
 }}}

 In addition dwm2's ''mtd-utils-mcast'' test program operated through this
 AP resulted in many lost packets if multicast UDP was used.  However a
 !MacBook doing a ''tcpdump'' at the same time also saw lost packets, so it
 is entirely likely to be the AP at fault.

-- 
Ticket URL: <http://dev.laptop.org/ticket/2136#comment:5>
One Laptop Per Child <http://laptop.org/>