As said, WDS is not a solution because you loose wireless AP function on both routers. It's like you dedicate the 2 WDS routers for ethernet bridge only and no wireless client can connect after that!
WHAT??
WDS does give you an AP on each router setup with WDS:
Wireless clients CAN connect to the CLOSEST of these APs that are part of the same WDS.
Main difference between WDS and client-bridge is simply that WDS would maintain and use the actual MACs of the devices connected to it, where client-bridge would send the AP's MAC address for each device connected to it.
Of course, in client-bridge, you can not connect wireless clients, but in WDS mode, the device is actually in AP mode and simply uses the MAC address of the other(s) APs in the WDS setup to communicate with each other and pass control messages for when wireless clients move from one AP to another, etc.
Unfortunately not with this router. When configured in WDS mode the AR670W does not give anymore the possibility to connect wireless client on any AP and the part that works is the Ethernet bridge clients only...Not a solution for me because I loose the 2 routers as Acces Points while in fact I need only a client bridge solution!
Maybe you turned off AP function in DD-WRT. It's possible to do that if you issue the following commands.
nvram set wl0_mode=wds
nvram commit
reboot
Thanks for you reply,
Is your setting with 2 AR670W or just one of them? I know that WDS is not cross platform compatible and for this reason I use 2 of them, one as main AP router and one want to use it as a client ethernet bridge mainly.
Maybe you turned off AP function in DD-WRT. It's possible to do that if you issue the following commands.
nvram set wl0_mode=wds
nvram commit
reboot
Thanks for you reply,
Is your setting with 2 AR670W or just one of them? I know that WDS is not cross platform compatible and for this reason I use 2 of them, one as main AP router and one want to use it as a client ethernet bridge mainly.
That would seem not to be the case as people have had linksys and this model hooked up together.
Its not supported but this doesn't mean it doesn't work.
Posted: Tue Mar 09, 2010 16:55 Post subject: No WDS nor Client-Bridge with TWO ar670w and 160n(v3)
I've been trying since December with every firmware release and every combination imaginable to get my three access points to connect together on a single subnet but no go so far.
They work great in basic Client mode which is okay and fit my original need.
I'd like to get them all routing on the same subnet for another application if that's possible.
If needed, with some advice, I can reconfigure and dump the configs for all to review. Also, I really only need two access points so if need be, can remove one from the network to eliminate complexity.
In my testing, I had AP1 as Edge39, AP2 as Office39, and AP3 as Back39. LAN 192.168.39.0/24. I can disable WPA2/AES but didn't seem to have any trouble with it.
Posted: Tue Mar 09, 2010 18:00 Post subject: Re: No WDS nor Client-Bridge with TWO ar670w and 160n(v3)
deckrunr wrote:
I've been trying since December with every firmware release and every combination imaginable to get my three access points to connect together on a single subnet but no go so far.
They work great in basic Client mode which is okay and fit my original need.
I'd like to get them all routing on the same subnet for another application if that's possible.
If needed, with some advice, I can reconfigure and dump the configs for all to review. Also, I really only need two access points so if need be, can remove one from the network to eliminate complexity.
In my testing, I had AP1 as Edge39, AP2 as Office39, and AP3 as Back39. LAN 192.168.39.0/24. I can disable WPA2/AES but didn't seem to have any trouble with it.
Joined: 05 Jan 2010 Posts: 571 Location: Orlando, FL
Posted: Wed Mar 10, 2010 18:47 Post subject: Re: No WDS nor Client-Bridge with TWO ar670w and 160n(v3)
deckrunr wrote:
I've been trying since December with every firmware release and every combination imaginable to get my three access points to connect together on a single subnet but no go so far.
They work great in basic Client mode which is okay and fit my original need.
I'd like to get them all routing on the same subnet for another application if that's possible.
If they are all AR670W you can set up WDS, then add a VAP to each unit that you also want to use as an AP. _________________ Linksys 610Nv2 DD-WRT v24-sp2 (03/24/10) mega - build 14144
Posted: Fri Mar 19, 2010 7:01 Post subject: WDS with VAP?
I guess the subject line gets overlooked - my hardware is:
Two Airlink ar670w and one Linksys 160n(v3).
--
I usually test with just the two airlink APs.
I'll see if adding VAP magically fixes WDS. I remember ppl posting that in their howtos. I believe I tried that back in December but it can't hurt to try again.
I'm in a similar situation, hardware wise. I have 2 AR670W's, with DD-WRT on both, and I can't get them to see each other. Not sure if I'm just overlooking something or what. I was trying to get WDS to work, so I can use it for my 360's connection.
You just enable WDS on both, set the MAC address for each one in the opposite router (for LAN), and it should work, right? Wasn't sure about encryption, or setting up extra VAP's, or anything like that. I don't need any wireless set up right now. I just have my main PC, and the 360, and that's all I want on it at this point. So, if someone could, could you give me a step-by-step guide on how to set up a secured, WDS setup for my needs? I'd really appreciate it.
Posted: Wed Mar 24, 2010 3:41 Post subject: Using WDS mode
Make sure you set the Routers AP mode, to the same channel and not auto-configure. The secondary should not have the DHCP enabled, and you should try to get them linked before you enable any encryption. Also make sure your using the Wireless Mac address and not one of the others that can be listed on the status page.
