Recent content by terminator

Just wanted to update that I tried aimesh again with AX58U merlin 386.7_2 and node AC66U_B1 as stock 3.0.0.4.386_49703-gc2cdfc8. Something much have changed somewhere because this is working pretty good so far! It was not a fresh install - I just in-place update for both. Will try not to update...

@eibgrad that might work. I am not proficient in firewall rules. Can this be easily changed to do it for only one IP all traffic?

Thanks, I have hit certain conditions which turns the VPN client OFF which turns the killswitch off even when auto start is enabled. I can't imagine I would be the only one hitting these conditions. The first time it happened is right after I applied the firmware upgrade. The only reason I...

@eibgrad - the information helps. Thank you so much. @RMerlin - Anyway to add a flag "Persist when off" or something by any chance? As you can see from the above use case, it was off after restart, the client connected and did torrenting and now I might get a letter from the ISP :(

I am using AX68u on 386.3_2. I have the VPN client setup and 1 IP/machine is set to route all traffic through it. "Killswitch - Block routed clients if tunnel goes down" is checked. Now, if I change the VPN server IP address to put it in an error state, killswitch works correctly and the...

The unreliability connection issues I had -- just for the aimesh nodes were not resolved in 386.2. Some people are experiencing these and some are not so unsure what is going on. At least for me, if I unplug all the aimesh nodes, all is good. There was "aimesh 2.0" in 386.1 so to some extent the...

Other than this Aimesh issue, I have no other issues. I run a moderate setup - Static IPs for a few clients, DNS name updated for several clients, VPN Server, VPN Client, Diversion using amtm, 1 Guest Network. AiProtection, Adaptive QOS , AICloud, etc are OFF

Also, AX58U by itself as the main router works great. Worked great on 385, works great on 386 (currently all mesh nodes are unplugged). The problem seems to be with only the clients that connect to the nodes. It could have been the hardware of the node but both of them are doing the exact same...

Thanks I mentioned in the original post I have done factory reset several times (and then did not restore a backup file set everything up by hand). I usually run all merlin but have also tried merlin on the main router and asus stock on ai mesh nodes with the same result. Everything is cat 6...

Sorry forgot to mention that both mesh nodes are hardwired with cat 6. And the exact setup works if I go back to 385.

Up until 386 my Aimesh was working great. I have a AX58U as main and a couple of AC66U_B1 as nodes. Since 386 (and yes the latest one too) the aimesh nodes have gotten slow and sporadic for WiFi. As soon as a device connects to them, users complain of slow internet or no internet. I have 100...

As far as I am aware nothing else needs to be done. I live in a 4500 sq ft 3 story house and 2 are enough for strong signal everywhere - a third one sits idle for testing or if I need to plug one in for a better signal outside at times. I often also see that a device wouldn't connect to what...

ok, thanks! I want to install stock code and see if that changes anything so I can report the issue to Asus but I am being too lazy at the moment :)

@RMerlin - is there a way to easily tell if the issue is coming form core ASUS codebase or elsewhere?

Thanks for the update. I have different SSID for 2.4Ghz and 5Ghz and I am definitely seeing the issue on 5Ghz. Only a couple of legacy devices that don't support 5Ghz use 2.4Ghz at my house.