Good evening,
link to the issue : https://dev.openwrt.org/ticket/7335
I realize now that the issue is quite weird and that the original title is not
exactly fitting. Here are the results of my tests on a WRT54GL running
backfire, with serial port. FWIW, the unit at the other end of the WDS is also
a WRT54GL but running 7.09.
With the *original* broadcom.sh script shipped in backfire, what happens is the
following :
- if the only wireless interface defined is the WDS, it quite simply doesn't
work. iwconfig shows this :
wl0 IEEE 802.11-DS ESSID:""
Mode:Master Frequency:2.432 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:off Fragment thr:off
Link Quality:5 Signal level:0 Noise level:163
Rx invalid nwid:0 Rx invalid crypt:42 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
wds0.1 no wireless extensions.
- if an AP is defined alongside the WDS, both the WDS and the AP works. The
weird thing however is that when I use airodump to check for traffic, I do NOT
see the wds ESSID (it's not hidden though), and traffic going through the WDS
will actually appear in the AP ESSID (ie when pinging the unit, I see the
traffic count increasing on the AP ESSID even though there are no clients).
iwconfig shows wl0 in master mode, with the ESSID of the AP.
---
With the *patched* broadcom.sh, the situation is reversed, and more:
- if an AP is defined alongside the WDS, the AP is working but not the WDS,
although BOTH ESSIDs can be seen by airodump. iwconfig output shows a proper
wl0 interface set up in Master mode, plus the following:
wds0.1 no wireless extensions.
wl0.1 IEEE 802.11-DS ESSID:"wds"
Mode:Master Channel:5 Access Point: 02:18:F8:CC:CC:23
Bit Rate=54 Mb/s
RTS thr:off Fragment thr:off
- if the WDS is the only interface defined, it works properly with its own
ESSID. iwconfig show wl0 in master mode with the WDS ESSID. Still no wireless
extensions for wds0.1
On the positive side, it seems that WDS is capable of working with older
companions. But it's not always working when it should...
I am at a loss for an explanation, but I'd gladly help debugging this one if
one cares to tell me what to do :-)
Cheers,
Romain (Mr_Smoke on IRC)
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
