I did a recent re-compile for my ramips routers with the same config files - have several of the Netgear rt6700v2. Well, something happened - now I'm unable to ping my main router from the client WDS.
Setup: router A is the main router connected to fiber, serves the IP addresses via DHCP. It is also the WDS access point. Router B connects to A as a WDS client, acting as a repeater. My computer is connected to router B via the LAN ports (for debugging purposes). Router B is my WDS client/repeater.
The encrypted WDS connection seems good - both the client and the access point says strong signal. However I can't ping router A from my computer connected to B, hence B is not getting any internet. Can't get an IP address either. Router B has the default gateway set to be 192.168.1.1, the IP address of A. Both WDS is set to LAN.
What am I missing here? Why aren't they talking to each other even though they are associated? And what has changed in the past two months or so - this happened after recompinging my firmware (master).
If you're not using WDS, how do you bridge wirelessly to client? In my case, I'm using WDS as a wireless bridge between routers A and B over 5g so that I can extend my 2.4g signal outside to my little yard.
I use them with Pis because they add a lot of packages that would take up software memory.
And, I suggest them for pis because Pis need tweaking without those.
Also, I can bake USB WiFi (well anything) drivers in when I'm working in a locality that only offers WiFi and without those and then connect to the WiFi without trying to. With the devices ready to be purposely moved into the configuration. If the added packages do not compile you know before you try booting something that is glitchy.
Let us not forget that OP is having trouble with the normal stable. That build should work after firstboot->reboot.
But feel free to tutor them through BATMAN. I've never used it.
Why am I using a self-compiled snapshot on master - long story, but the short of it was that the r6700v2 (and many other routers) had issues with accessing the factory partition due to bad blocks. Looking back, I was dealing with it back in 12/22... others were working with that before it. A patch was created but never made it into master. Somehow after asking a few developers, they shared the patch and soon incorporated into master. During this time I learned how to compile, include packages into the build, etc. Lots of fun.
I tried 802.11s before settling on WDS, however I was getting throughput issues. Even with master built about 6 months ago, I was getting significant dropped packets. I couldn't figure out the problem/solution. It seemed specific to the chipset and hostapd, and some posts have said that it will be resolved when kernel 6.1 becomes available. With WDS working just fine and reliably (until now), I just stuck with WDS.
Enough background...
Don't think its a subnet issue - A is 192.168.1.1. B is 192.168.1.3 both with netmask of 255.255.255.0.
Not related to encryption either - set up a new ESSID without encryption and both AP+WDS and Client+WDS added to the LAN. Again, they associate with a strong connection, but it appears that I am still unable to ping one router from the other.
Awefully wierd problem because I haven't changed my .config file.
It turns out that I had just needed to do a "make dirclean" and recompile, and everything is back to normal.
Before the "make dirclean" I had even restored to factory default (thankfully I saved a configuration backup) and the routing didn't come back up.
I did a quick test of the throughput between a 802.11s link and WDS. On my setup with 5g, 80mhz, I got 250-350 MBits/sec through 802.11s and 450-550 MBits/sec. This is from a wired computer to the router itself (I know, its not a fast CPU). Months ago I was getting over 50% packet loss and abysmal transfer rates. Definitely improved.
I only have 1 wireless bridge. Would definitely consider using 802.11s + BATMAN if I move to a larger place needing another bridge. 5ghz bridge with clients connecting over 2.4ghz.
My biggest issue is that roaming between different routers on 2.4 ghz still isn't great. My phone will go to cellular before reconnecting. Kids' old tablets take forever to reconnect. This is with r/k/v etc. all installed. Any suggestions for this?
This has something to do with how aggressive roaming is in either the clients or devices but you say you have no problem at work, so, we know that device is working.
It is trivial to change this in windows but I do not see it on my iPhone or any of the android crap I have around. It is also called 'roaming aggressiveness'
Just to ensure I have this right:
Both routers are running OpenWrt, both are setup for WDS (which I have already admitted I have never used)
You have used repeater and bridge, seemingly, interchangeably. Which are you using? It definitely makes a difference.
So for the ping: Isolate clients is unchecked? Can you ping 1.1.1.1? Cloudfares dns server
From Wikipedia: All base stations in a wireless distribution system must be configured to use the same radio channel, ( I do not know if this means the base router to client too) method of encryption (none, WEP, WPA or WPA2) and the same encryption keys. They may be configured to different service set identifiers (SSIDs). WDS also requires every base station to be configured to forward to others in the system. (Why I asked if isolate clients is disabled.)