Posted: Thu Aug 09, 2018 23:35 Post subject: Unstable WDS - 2xDIR868L - v3.0-r36006 std (05/23/18)
I'm trying to run WDS but it is really unstable. I had it working this morning where I could log into both my 5GHz and 2.4GHz network and see both routers homepages. A few hours later, and the secondary router was inaccessible and all devices connected to that router were no longer accessible.
Primary router:
192.168.1.1
WL0 (2.4GHz) WDS: lists secondary router MAC address with LAN selected
Secondary router:
192.168.1.2
WL0 (2.4GHz) WDS: lists primary router MAC address with LAN selected
Set as Router under Advanced Networking
SPI Firewall, dhcp server, wan traffic counter off
Both:
WPS2 Personal (AES)
I get wireless status showing each other under WDS. No 0s, all coherent values. Still looks good when the secondary router is inaccessible.
I've enabled STP on both.
I've disabled SFE on both.
p.s: you can edit the wiki yourself. Just Register there (has to be done seperately from the Forum) and you are good to update the articles _________________ 2x Buffalo WHR-HP-G300N in AP
2x Buffalo WHR-HP-G300N in WDS (not working atm)
1x Buffalo WHR-HP-G300N in Wireless Client-Bridge (not working atm)
1x Buffalo WHR-HP-G300N in Reserve (still looking for that on ebay)
I don’t like 35531 (BS build) much. OpenVPN causes me problems even once I added necessary iptables rules. And WDS never comes back up when only one device is restarted. Still searching for a solution. mrjcd tested r36104 and confirmed WDS works for his devices. Gonna give that a try.
Interesting note when running 35531 is that when I replaced the client firmware with Tomato by Shibby, the WDS comes back up even when only the client router is restarted. Although it has very bad throughout 1-5Mbps. Not sure why that is.
I don’t like 35531 (BS build) much. OpenVPN causes me problems even once I added necessary iptables rules. And WDS never comes back up when only one device is restarted. Still searching for a solution. mrjcd tested r36104 and confirmed WDS works for his devices. Gonna give that a try.
Interesting note when running 35531 is that when I replaced the client firmware with Tomato by Shibby, the WDS comes back up even when only the client router is restarted. Although it has very bad throughout 1-5Mbps. Not sure why that is.
Please let us know how it goes! The last time i tried was few months back using netgear ARM routers and it didn’t work.
Finished some debugging. I could not get r36104 to work. I then upgraded to the latest 36808.
I was finally able to get the WDS link after I turned on wireless security (WPA2 Personal). With no wireless security the WDS link won't come up at all.
I then couldn't ping primary to secondary or vice-versa. I got that working by adding this line to the startup script:
brctl addif br0 wds0.1
That's it for now. Hopefully I'll get both routers fully up and running later today.
