Hi, I got a WDS bridge working between two WRT54GS routers running the latest official firmware (4.70.6). First I got a shell on the routers using BatBox Linux: http://www.batbox.org/wrt54g-linux.html Note that no permanent changes are done to the router firmware, BatBox Linux will use the tmp directory and will not persist across reboots. Then I issued the following commands on the first router: Code: nvram set wl_afterburner=off nvram set wl0_afterburner=off nvram set wl_wds=WIRELESS_MAC_ADDRESS_OF_SECOND_ROUTER nvram set wl_lazywds=0 nvram set wl0_lazywds=0 nvram commit reboot And I issued the following commands on the second router (the only difference is the mac address): Code: nvram set wl_afterburner=off nvram set wl0_afterburner=off nvram set wl_wds=WIRELESS_MAC_ADDRESS_OF_FIRST_ROUTER nvram set wl_lazywds=0 nvram set wl0_lazywds=0 nvram commit reboot When the routers came back after the reboot, the WDS brigde was already working fine! Then I enabled WPA with AES in the web interface for both routers and it worked fine too! BTW, I get more than 20Mbit/sec out of the WDS bridge with the official firmware with WPA enabled, while I got only about 8Mbit/sec with Alchemy 1.0. There is small issue I couldn't figure out yet: the 'wl_lazywds' and 'wl0_lazywds' settings always revert to '1' after reboot, even after I set them to '0' and issued an 'nvram commit' before reboot. Any idea? Anyway, since I have WPA enabled, it shouldn't be a big deal, since none should be able to connect to my Wi-Fi routers anyway, right? Thanks to the great users of these forums that make this happen. Regards.