I'm also seeing the 2.4GHz issues reported by others (particularly @ElmerFudd) with TP-Link bulbs and switches going offline or slow to respond after upgrading to 386.4 on my AX88U where these problems did not previously exist.
The only workaround I have found to work, apart from reverting to a...
What I mean is you should change your general DHCP pool back to the full default range 192.168.xx.2 - 192.168.xx.254 regardless of what DHCP reservations you specify.
Let the router manage the reservations within the full default general DHCP pool; you don't need to carve out a range for the...
I have not had problems connecting more than 60 devices to my AX88U.
For me, I also have several DHCP reservations, but spread across the default IP range 192.168.1.2 - 192.168.1.254
Beyond aesthetics, any reason why you are specifying one range for reservations and another for everything else...
That's exactly one outcome of the issue: I have to restart my VPN client (either manually or via script) after router reboot to workaround the issue.
As for spdMerlin, I've found that running Speedtest on the router does not max out my ISP service plan. I've read it's got to do with the fact...
After rebooting my RT-AX88U, hardwired OpenVPN client Speedtest download results are typically ~120 Mbps.
If I then restart the OpenVPN client (either by toggling its 'Service state' setting or restarting it through scMerlin), the download results increase dramatically to ~190 Mbps.
Digging...
That's interesting and something I will experiment with.
Though it's unlikely I'm getting ~200 Mbps VPN throughput without AES-NI acceleration; this figure is also in line with RMerlin's hardware-accelerated VPN test results in a thread I came across previously.
And there's this he says...
Just an update that I'm working around this problem by restarting the VPN client via user script on router reboot.
Still very curious to chase down a true fix or explanation, but I think there's not much else I can do for now due to my limited knowledge.
I am sorry to hear about your problem. It's similar to mine, but seems to be a clearly different problem.
Mine is 100% CPU usage for bcmsw_rx with, and only with, VPN traffic, thereby causing VPN throughput degradation on Speedtest experiments. This issue does not resolve itself with time, but...
Good question.
It was with policy rules; I just tested with VPN completely off and it's the same behavior with [bcmsw_rx] at ~50% during Speedtest download.
I got it from the PIA website; though I did make some manual changes and custom configuration.
As a test, I disabled my existing OpenVPN client and created a new one from scratch using the default config file from PIA (us_california.ovpn).
The results are unfortunately the same. And there's...
Link aggregation has always been disabled.
And so has IPv6 (from IPv6 > Connection type).
I don't see any IPv6 commands in my VPN profile (in VPN > VPN Client) so don't know how to do what you are suggesting.
Thank you!
Hello,
Almost always after a router reboot (but not 100% always), the [bcmsw_rx] process will consistently run at 100% CPU during my hardwired VPN speed tests with resulting download speeds at ~120 Mbps.
The unexpectedly high CPU usage at 100% is what I am concerned about along with the...