Posted: Sat Dec 04, 2021 22:27 Post subject: [SOLVED] WRT1900ACSV2 wifi clients isolated after reboot
Hi
For some time now I have an issue with my router setup which causes strange isolation behaviour after router reboot.
When the router starts all wifi clients seem isolated from one another, they can only see wired clients.
It all goes away if I run the "startservice lan" command.
The rouiter is on the 47745 firmware, but the issue was present in 44048 as well. I did reset it to factory and set all the configurations. What I noticed is that during the setup that behaviour was not there. It only started somewhere at the end of configuration so I assume it is caused by some of my settings.
What I checked is whether the isolation is not actually turned on (it isn't) and if the interfaces are bridged correctly (they are).
Did anyone noticed this kind of behaviour and maybe found the cause?
Last edited by deshark on Tue Dec 07, 2021 21:35; edited 1 time in total
Joined: 04 Aug 2018 Posts: 1447 Location: Appalachian mountains, USA
Posted: Sun Dec 05, 2021 15:56 Post subject:
Try nvram show | grep ap_isolate (reports on a different type of isolation). _________________ 2x Netgear XR500 and 3x Linksys WRT1900ACSv2 on 53544: VLANs, VAPs, NAS, station mode, OpenVPN client (AirVPN), wireguard server (AirVPN port forward) and clients (AzireVPN, AirVPN, private), 3 DNSCrypt providers via VPN.
Is there something in the wlan startup routine that kicks in after, let's say, an hour? I left the router without a restart for a couple of hours and the wlan clients started to see each other. I have to test that behaviour. Anyway they still seem isolated for a long time after every boot.
Just checked again. I rebooted the router around the time I posted the previous message. In the last 15 minutes the wifi client started to see each other.
Something changes around an hour after the reboot and stays fine after that. (at least I have not noticed it going back to the isolated state)
Any ideas where to look for an answer? What might be happening?
Did some more tests, and the router "fixes" itself exactly (to the minute) one hour after the reboot.
Unfortunately most of my wireless clients don't have the ability to run any network tools so it is hard to debug deeper and log the results for any analysis.
I know the network is broken "just" for one hour after each reboot. Also I can always fix it sooner by running "startservice lan"
I wish I could get to the bottom of this behaviour, but it is just not worth the time
This is where we have to start looking at all of your wireless settings. Are you running anything in startup or via cron that may affect this?
I have a firewall script for my Wireguard tunnel:
iptables -t nat -I POSTROUTING -o br0 -s 10.10.20.0/24 -j MASQUERADE
I also have cron entry:
* * * * * root /opt/scripts/cpu_temp
Which runs script that reads the temperature of the router CPU and notifies me if it exceeds a set threshold.
nothing else in terms of scripts.
What values from WiFi settings might be responsible for the behaviour I am experiencing?
Just to stress one more time. None of my scripts modifies any of the router wifi or network settings, and still one hour after reboot it starts to work correctly.
