Printable View
Yesterday I found information about this. Apparently the WDS standard does not support WPA encryption and we're stuck with WEP. Something to do with sharing certificates not supported on access points.
Here is the link to this info: http://www.tomsnetworking.com/Sections-article78.php
It also has a link to a PDF file which explains WDS in more detail.
Hope thi helps,
Bogdan
Yes I can confirm that the WDS standard is restricted to using WEP. Once you understand WEP it is not that complicated.
Also it seems true that you will lose 50% of the wireless transfer speed since both incomming and outgoing packets will pass thru the WDS as WiFi.
Hence, I strongly suggest to all people that want to expand the range of a wireless network to use a plain old UTP cable between the Gateway or a Broadband Modem and your remote Wireless Access points.
I can confirm that using 1.8.1.7-2a there is NO problem with WDS and WPA-PSK/TKIP!!!
(using same SSID on both 500g!)
Hi,
i have experienced the same problem during the setup of my 2 WL500g's (both running newest 1.9.2.7-4 firmware). It is probably an error in the firmware but i am not sure, it can be an error in my setup.
The setup is following:
DSL modem -> WL500g (HG mode, WPA/AES, WDS only, advanced mode "AP or WDS"), other WL500g (AP mode, WPA/AES, Hybrid mode, advanced mode "Ethernet bridge", running DHCP only). Both are using same SSID, of course.
Is it generally possible to setup them with WDS using WPA/AES or not ?
Regards, El Vino
Please check Known Bugs Section in the FAQ.
"9. WDS using WPA encryption does not function. No connection is established.
Affected versions: all stock firmwares except firmware 1.8.1.7"
Now, which one 1.8.1.7 is meant here ? custom ? which build number ?
:confused:
This bug list if for stocks firmwares only. So, every firmware based on the 1.8.1.7 should work, including stock 1.8.1.7 and custom 1.8.1.7-x.
Yeah, finally, it works !
I set it up with custom firmware 1.8.1.7-3 on BOTH wl500g's.
Thank you very much Oleg, you did a great job ! :cool:
Regards, El Vino
Hi !
i was running 2 WRT54G (with openwrt) and the wl-hdd in wds mode (aka hybrid on asus) now i changed firmware on wl-hdd because i need nfs server stuff for my sat receiver. but now the wl-hdd does not connect to the other one i set channel WEP and ssid the same like on wrt (in wrt the mac address is still in) but nothing....
any hints ?
Ciao Gerd
Hello all
I need to establish a WDS link between buildings to interconnect two Ethernet LANs. I have two WL500G successfuly connected in WDS mode, so this part of the equation has already been solved.
It would be convenient to organize the LANs as two segments; one from, say, 192.168.0.1 to 192.168.0.127 and the other from 192.168.0.129 to 192.168.0.255. Does anyone here have some experience at doing this? How should the 500G's be configured, with regard to routes? Should I connect the WAN port on each side to the respective wired segment or use just the LAN ports? Must I use only one LAN segment for both sides? This would be inconvenient, since each side has its own Internet access via ADSL routers and I want to avoid confusions with DHCP etc.
Thank you for your help.
I suppose I commited a error/omission in my previous message: I said "two segments" but perhaps I should have said "two subnets" with network mask 255.255.255.128
Does this help to understand my question?
Thank you!
Best way to do this is remove the WLAN interface from the bridge, setup a small segment for it and adding static routes. This cannot be done from the web interface AFAIK, but when logging in with telnet/ssh, you can issue these commands. You can test things and if it works, you can store them in the post-boot file to make the WL-500g load them on startup.
On box 1:
brctl delif br0 wds0.49153
ifconfig br0 192.168.0.1 netmask 255.255.255.128
ifconfig wds0.49153 172.16.0.1 netmask 255.255.255.252
route add -net 192.168.0.128/25 gw 172.16.0.2
On box 2:
brctl delif br0 wds0.49153
ifconfig br0 192.168.0.129 netmask 255.255.255.128
ifconfig wds0.49153 172.16.0.2 netmask 255.255.255.252
route add -net 192.168.0.0/25 gw 172.16.0.1
Basically what happens:
- Break the WLAN apart from the LAN
- Set the LAN (br0) IP-address, (line 2 may be removed if you set this IP in the web interface)
- Set IP address on WDS interface
- Add route to other network via WDS to other WL-500g box
Also note the WDS might have a different name, but on my three WL-500g boxes the first WDS link has this name (the second WDS link has wds0.49154), but I don't know where these numbers come from and if they're the same allways. Looking up with ifconfig gives you a truncated name (missing last digit), but you may try "ip link" to find the correct name.
I must thank you for the attention you gave to my question!
I will surelly try the steps you wrote and I will report back later.
Thank you again :)
hello i have setup 2 WL500G
1 - Primary with Internet Connection. (Should be host)
2 - Slave with connection to the Primary...
i've added both of there MACs in connection list
but it seems that they fight over which one to be HOST
how to setup ??
please ...
i've looked through the manual an it says nothing about it...
I tried the steps you indicate but the thing doesn't work. It seems the devices don't route between the eth0 and wds0.49153 interfaces. I only obtain a connection when both 500Gs are on the same subnet. Otherwise, the response to a ping is always the same: "Destination net unreachable".
I suppose I need to use two subnets because each one of the 2 LANs I want to interconnect has its own Internet access via a ADSL modem router wich also functions as a DHCP server. I don't want the computers from one LAN to access the ADSL router on the other building and much less do I want them to see two DHCP servers on the network...
Your approach seems correct to me but something is wrong with the routing function.
Thank you again!