WDS: iwconfig does not show correct mode?

Sat Dec 13 20:38:36 PST 2003

On Sunday 14 December 2003 05:56, vda at port.imtp.ilyichevsk.odessa.ua wrote:
> It worked. But AP1 lost all the other STA associations.
> iwconfig shows *both* wlan0 and wlan0wds0 to be repeaters!
> Thats probably not right.
>     iwconfig wlan0 mode master
> fixed that *without* losing wlan0wds0 link! Wow!
> Now iwconfig shows wlan0 and wlan0wds0 as masters.
> This is not right either, but I suppose it's simply not true and wds0
> is a repeater in reality?

Heh. On the AP2 I tried
    iwconfig wlan0 mode managed
and it worked too! Now AP2 have two functioning links to AP1:
one is a STA->AP over wlan0 and one WDS over wlan0wds0. 8)

iwconfig shows both wlan0 and wlan0wds0 as 'managed'.

Heavy pinging thru both links with
    ping -i0.01 -s1400
worked with following throughput figures:
# nmeter t nwlan0 nwlan0wds0
06:20:03 wlan0 136k 140k wlan0wds0 136k 139k
06:20:04 wlan0 136k 138k wlan0wds0 136k 139k
06:20:05 wlan0 133k 139k wlan0wds0 135k 138k

Even heavier ping -i0.005 -s1400 killed hostap
on the AP1 within minute.
Syslog started to fill with lots of errors.
See below signature. Full log is available on request.
After some tens of seconds, hostap was able to reset wlan0:

06:33:32 wlan0: hfa384x_setup_bap - timeout after
06:33:32 wlan0: prism2_tx - to BAP0 failed
06:33:32 wlan0: scheduled card reset
06:33:32 hostap_pci: wlan0: resetting card
06:33:32 prism2_hw_init: initialized in 200 ms
06:33:42 NETDEV WATCHDOG: wlan0wds0: transmit timed out
06:33:42 wlan0wds0 Tx timed out! Resetting card
06:33:42 wlan0wds0: CMD=8021 EVSTAT=0000 OFFSET0=0000 OFFSET1=0000 
SWSUPPORT0=8a32
06:33:42 wlan0: scheduled card reset
06:33:42 hostap_pci: wlan0: resetting card
06:33:42 wlan0: removed pending cmd_queue entry (type=0, cmd=0x0021, 
param0=0xfdc6)
06:33:42 prism2_hw_init: initialized in 200 ms
06:33:42 wlan0: hfa384x_cmd: command was not completed (res=0, entry=cbd2b4e0, 
type=0, cmd=0x0021, param0=0xfdc6, EVSTAT
06:33:42 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fdc6, 
len=12)
06:33:42 prism2_tx_timeout: wake up queue

and both pings were running again, but within a minute everything repeats.
--
vda

06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b220, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fdc6, 
len=12)
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b220, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fdc6, 
len=12)
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b220, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fdc1, 
len=2)
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b220, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc06, 
len=2)
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b220, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc28, 
len=2)
06:25:44 CNFWEPFLAGS reading failed
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b220, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd42, 
len=6)
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b1e0, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc0e, 
len=34)
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b220, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc84, 
len=2)
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
06:25:44 wlan0: hfa384x_cmd_issue - timeout - reg=0x810b
06:25:44 wlan0: hfa384x_cmd: entry still in list? (entry=cbd2b220, type=0, 
res=-1)
06:25:44 wlan0: hfa384x_cmd: interrupted; err=-110
06:25:44 wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc83, 
len=2)
06:25:44 wlan0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec