Configuring WDS.

[coprocessor]

Not sure if this is the correct section to post my query. Here is what I would like to achieve:

Room 1 already has a modem connected to the internet which is connected to a Wireless Router (DIR-605L). I would want to use another spare DIR-524 router in stock to extend the range under one SSID with WDS. I'm currently trying to set it up in the following manner:

1. On the DIR-524, set the same SSID, channel and pre-shared key as DIR-605L.
2. Disable DHCP and assign a static IP to the DIR-524 which is in the same range. (Example: If Room 1 router IP is 192.168.0.1, Room 2 router IP is 192.168.0.110)
3. Under the WDS option on the DIR-524, specify the main router's (DIR-605L) MAC address.
4. Disable Bridge Restriction.

Post this, I placed the second router (DIR-524) close to one of my laptops to test if it worked. It did pick up the DIR-524's SSID but was unable to communicate to the main router (DIR-605L). Also, the IP accquired is 169.x.x.x

Any suggestions to rectify this so the both the routers can talk to each other wirelessly??

PS: I would not like to hard wire the second router to the main one because of cabling feasibility issues.

 

[avos]

First you should realize that WDS is not a standard and can vary between different chipsets. The 605L and 524 are both sold by d-link, but one uses a realtek chipset, the other uses artheros. It is possible that even when configured properly WDS will not work between them.

The biggest hurdle is usually encryption. I would first try doing it with open wireless. I have ran across some manufactures that will only do WDS with either open or WEP (which is as good as open these days).

If it is possible to create a wireless bridge instead this might be a better option. I'm not familiar with what d-link offers with its firmware. Have the one with the wireless devices connecting to it as the host and the one with the modem connected to it as the client. Then set the default gateway as the router connected to the modem.

An IP of 169.x.x.x is just windows assigning itself an ip when none is given to it through dhcp.