I had two WRT54GL with WhiteRussian and a working WDS config... I tried an update to the latest Kamikaze (with 2.4 kernel) but I do not get WDS to work...

Tried the LuCI to configure the WDS as well as some manual configurations... Got through almost every forum post I could find, tried almost every configuration.. No luck....

Her is (one of the many) config(s i've tried out):

Router1

config 'wifi-device' 'wl0'
    option 'type' 'broadcom'
    option 'channel' '5'
    option 'disabled' '0'

config 'wifi-iface'
    option 'device' 'wl0'
    option 'ssid' 'MYSSID'
    option 'network' 'lan'
    option 'mode' 'ap'
    option 'encryption' 'psk2'
    option 'key' 'mypsk2key'

config 'wifi-iface'
    option 'device' 'wl0'
    option 'network' 'lan'
    option 'mode' 'wds'
    option 'bssid' '00:18:39:xx:xx:xx'
    option 'encryption' 'none'

----------------------------------------------
Router2

config 'wifi-device' 'wl0'
    option 'type' 'broadcom'
    option 'channel' '5'
    option 'disabled' '0'

config 'wifi-iface'
    option 'device' 'wl0'
    option 'ssid' 'MYSSID'
    option 'network' 'lan'
    option 'mode' 'ap'
    option 'encryption' 'psk2'
    option 'key' 'mypsk2key'

config 'wifi-iface'
    option 'device' 'wl0'
    option 'network' 'lan'
    option 'mode' 'wds'
    option 'bssid' '00:18:39:xx:xx:xx'
    option 'encryption' 'none'

--------------------------------
bssid is respectively wl0-MAC of other router

I've also tried with same ssid (for ap and wds-config), as it worked this way on WhiteRussian. And with MYSSIDWDS as SSID....

No luck.... No packets through the wds0.1 interface (which is up on both)

Has anyone a working WDS config on 2 WRT54GL?

I do not want to get back to white russian ;-)

Thanks

I have a similar problem.  My two routers are WRT54G (v1.1 and 2.0), although one of my routers is running HyperWRT-2.1b1+thibor-15c.  This has a WebUI option to run the router as an Access Point + WDS.  The other is running OpenWRT Kamikazee (r14113) and I can't find any option to set the router as WDS under the default WebUi LuCI.

Was going to try as suggested in this thread but it doesn't sound as though it will work based on the above?

(Last edited by slack---line on 2 Mar 2009, 23:21)

It should be in Administration -> Network -> Wireless -> wl0  Mode: WDS
Keep in mind that this only works for brcm-2.4 when you're on Broadcom hardware.

(Last edited by jow on 3 Mar 2009, 01:06)

Hmm I only have the following listed under Administration -> Network -> WiFfi (Wireless) -> wl0...

Access Point
Ad-Hoc
Client
Psuedo Ad-hoc (ahdemo)
Monitor

This is on Kamikaze (8.09 r14127) so thats running a 2.6.25.17 and I've therefore no hope?

Sounds as though I need to drop  back to White Russian to get WDS working properly, but I'm not sure what you mean by brcm-2.4?

For Broadcom-based platforms, you can run Kamikaze with the 2.4 kernel or the 2.6 kernel. The proprietary Broadcom drivers only work with 2.4. The open-source wireless driver works with 2.6, but it doesn't support WDS yet. So if you want WDS right now, you need to go with the 2.4 variant of Kamikaze, the one labeled brcm-2.4.

I thought WDS is possible in the latest open-source driver? How long might it take and what might be the problem to put WDS into Kamikaze 8.09 (2.6 kernel) ?

Regards,
Ced

I know this thread is a couple of months old... so I dunno if there's another thread that contains what I'm about to post... but I was struggling with WDS when I figured out a way to set up a node as an "AP" operating in WDS mode without using two separate SSID's.  I am using two ADI Pronghorn Metro router boards (atheros chipset) with one mini-pci radio in each.
Here is the code for the first router acting as an AP:

root@MERC_AP:/etc/config# cat wireless

config 'wifi-device' 'wifi0'
        option 'type' 'atheros'
        option 'disabled' '0'
        option 'channel' '6'
        option 'diversity' '0'

config 'wifi-iface'
        option 'device' 'wifi0'
        option 'network' 'lan'
        option 'mode' 'ap'
        option 'encryption' 'none'
        option 'ssid' '21S365'
        option 'wds' '1'
        option 'bssid' '00:15:6D:XX:XX:XX'

And here is the wireless config code for the second router acting as the client:

root@MERC_Client:/etc/config# cat wireless

config 'wifi-device' 'wifi0'
        option 'type' 'atheros'
        option 'diversity' '0'
        option 'channel' '6'

config 'wifi-iface'
        option 'device' 'wifi0'
        option 'network' 'lan'
        option 'mode' 'ap'
        option 'ssid' '21S365'
        option 'encryption' 'none'
        option 'wds' '1'
        option 'bssid' '00:15:6D:XX:XX:XX'

Note that both are set to AP mode, but there is an option called "WDS" that is enabled using "1".  This is instead of setting up two separate interfaces, one in AP mode and the other in WDS mode on each device.  The BSSID is the MAC address of the other router you would like to connect to.

At this point, it seems like this solution will only work if you want to wirelessly connect no more than two devices, but I hope this helps.

(Last edited by Jim@JHUAPL on 7 Jul 2009, 16:47)

Hi Clews
Did you manage to resolve your problem or did you go back to with russian ?

Richard

The configuration Clews used is not valid for atheros. The AP-to-AP WDS with BSSIDs is only used on Broadcom proprietary.
Corrected configuration below.

root@MERC_AP:/etc/config# cat wireless

config 'wifi-device' 'wifi0'
        option 'type' 'atheros'
        option 'disabled' '0'
        option 'channel' '6'
        option 'diversity' '0'

config 'wifi-iface'
        option 'device' 'wifi0'
        option 'network' 'lan'
        option 'mode' 'ap'
        option 'encryption' 'none'
        option 'ssid' '21S365'
        option 'wds' '1'

root@MERC_Client:/etc/config# cat wireless

config 'wifi-device' 'wifi0'
        option 'type' 'atheros'
        option 'diversity' '0'
        option 'channel' '6'

config 'wifi-iface'
        option 'device' 'wifi0'
        option 'network' 'lan'
        option 'mode' 'sta'
        option 'ssid' '21S365'
        option 'encryption' 'none'
        option 'wds' '1'

BSSID is not needed and one of both peers must be in Station mode.

Ok thank you for the response but the it seems that Clew had a config with Broadcom, no ? 
It's  Jim@JHUAPL who used atheros...

In fact my question is :
In the first post of Clews was the configuration ok correct for Braodcom ( despite the 2.6 kernel problem) ? 

Thx
Richard

Oops, you're right.

Jim@JHUAPL had atheros and an invalid config.
The config by Clew is almost correct, but the WDS ifaces _must have_ the same crypto settings as the AP. So he'd need to add

    option 'encryption' 'psk2'
    option 'key' 'mypsk2key'

To both WDS wifi-iface sections.

Some more clarification:
Clews' config is only applicable to brcm-2.4. The one from Jim@JHUAPL would be the one to use for Kernel 2.6, egardless of the wifi driver.

So I wil try to enable the WDS on my two WRT54GL...

Hope it will works !
Thx for responding.
Richard