[baggywrinkle]

I am trying to get WDS running on a pair of D-Link 868L, both HW revision B.

I am using the latest code v3.0-r34411 std (01/07/1.

I can get this running from a fresh default configuration. However as soon as I start to configure it into my environment, using a 10.x.x.x range, change the SSID from default DD-WRT and change to WDS2 it stops working.

I had it working following a factory reset, so I do know it will work managed this multiple times. But as I stated I gradually change things, reboots after each small change and noting. I have changed:

SSID; Network Mode (AC-Only); Channel Width (80Mhz); Extension Channel (lower, upper); Channel (136), WPA2, MSTP (on). All was OK, then started doc change IP address, DNS servers, etc and it stops working. Checked, double checked and triple checked everything.

I end up with one reporting the WDS Node as available on the Status; Wireless page, and the other showing no signal. Reboot and power cycle and they can swap roles.

I am new to DD-WRT and the tools, so nots are how too bug and look at what is wrong. Any help or guidance welcome. I have followed all the numerous guides on the internet for Broadcom based WDS and just can't get it back working.

[FurryNutz]

So using default settings and IP addresses on the main host router work?

[baggywrinkle]

[baggywrinkle]

Please note there is a mistake from my testing, the screen shots show two different SSID's. Changed one so that the SSID was "Baggywrinkle Backhaul" on both and still not working, one shows signal and the other doesn't. They are no more than 10m apart

[FurryNutz]

Well, I know that if you turn OFF the WDS bridged unit. Then change just the IP address of the main host router to what you want. Lets leave DNS and NTP along for right now. After changing the host routers IP address, save apply and reboot and IP addresses are still accessible there using a test client, both wired and wireless should be good.

If good, then I would turn on the WDS bridge, it should connect to the specified SSID name from the main host router and connect to that SSID Name. It should acquire the new IP address string coming from the main host router and be assigned something for the WDS bridge unit. Nothing on the WDS unit should be configured for any IP address, DNS or NTP. It should automatically get all that from the main host router.

[ian5142]

What do you mean changed it to WDS2?

Did you follow the Broadcom section in the wiki: https://www.dd-wrt.com/wiki/index.php/WDS_Linked_router_network#Broadcom_Based_Devices

[baggywrinkle]

[ian5142]

I would change the IP address before changing any other settings. Then setup WDS.

[FurryNutz]

Your breaking the WDS unit by changing it's configuration.
Don't change the configuration on a WDS unit. It gets it's address configuration from the main host router. Change the configuration on the main host router first.
Then just connect the WDS unit to the main host router and leave it.

[ian5142]

The WDS client does not get its address from the WDS AP, it is set by the WDS client itself, it must be in the same subnet as the WDS AP though.

[FurryNutz]

Roger that.

[baggywrinkle]

Yep, configured a static route on both units.

[baggywrinkle]

OK, Played around with it today, and sort of got it working. But not reliable.

It seems that the Wireless Security and WPA2 stops the devices from connecting properly. That said, even with WPA2 turned off, I can get them to connect reliable, but more reliable than with WPA2 on. From what I have read it should work. Have checked and double checked the key and it is correct as a standard client can connect.

I have however had stability issues. As soon as I put any load on it the two routers say they are connected, but no traffic flows.

Also the GUI never reports through the status; wireless screen any RX packets, yet running the command "wl -i wds1.1 pktpcnt" does show RX. TX packet count in the GUI does increase. Even a tcpdump -i wds1.1 only shows transmit traffic and no receive, but traffic is certainly flowing through the wireless and was link.

I have also had both routers stop reporting the 5Ghz interface as being their within the web interface. Again the command line shows everything their. A reboot fixes this.

Seems that something isn't quiet right, and nots are if it is hardware or software. Are there any logs or debuting that can be turned on.

Many Thanks

[quarkysg]

[ian5142]

Set up a Keep Alive (Connection Watchdog).
Set the WDS Station (the secondary router) to reboot every 300 or 1000 seconds. Use the ip of the main router in the blank. (Admin - Keep Alive tab).

As for stability, I have no idea. I use WDS on the Atheros side where it has been very stable for me. Pain in the butt to setup but it does work well.

I do put all of my MACs in each other's WDS MAC table, with the LAN option (Wireless - WL0 tab). Change the disable to LAN, then put in the wireless MAC of the other router. Then put in some human recognizable name (I usually use the name of the router). Click Apply.