Recent content by MarkusI

Those I tested with are daisy chained. Does that make a difference?

Running my AX88U-PRO in an AiMesh setup with multiple (old) nodes (AC68U, AC86U). Today I added two more nodes in a separate area of the site. I want the new (still old hardware) nodes to provide a different guest network than the others. So, I configured a second guest network and assigned it...

Strange... Do you also regularly reboot your central router? Do you know if the disconnect rate increases depending on how long since the last reboot of central and node router? If you have the possibility, you might want try if the stock firmware provides more stability.

We have a relatively huge AiMesh setup (1 AX88U-Pro now as central node, 3 AC86U nodes, 3 AC68U nodes) on a remote location. Generally, the AC68U nodes run very stably in our setup, but they are screwed, if they need to connect to an AC86U via Wifi, since AC86U sometimes runs into Wifi stability...

Do you experience stability issues on your router, too?

Not an expert, but as far as I understood, 'nvram get' will hang when the nvram issue occurs... The script then kills those hung 'nvram get' calls. Thus, it is not OpenVPN but getting the OpenVPN status (e.g. when browsing the admin UI). Unfortunately, as it looks in your case, the script does...

Ah, great you saw that!👍 Will it be part of the upcoming builds then?

Regarding the rules, you're right - I didn't check it in verbose mode. I have a RT-AX88U-PRO and VPN is configured to INTERNET only. I can 100% reproduce the issue every time if I reboot the device. I checked what happens if I configure VPN to BOTH with the following result Chain OVPNSF (1...

Sure: Directly after a fresh boot: Chain OVPNSF (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- any tun21 !192.168.1.0/24 anywhere 0 0 ACCEPT all -- tun21 any anywhere...

it somehow always adds ACCEPT all -- anywhere anywhere as last line (sometimes twice) your hint service stop_vpnserver1 iptables -F OVPNSF service start_vpnserver1 still works, though (until reboot)

@RMerlin just updated to beta2 and I still can ping all my internal IPs except the router itself when connected via OpenVPN and server is set to 'internet only'...

You mean on client or on server side? Client side shouldn't be important because I don't want to allow the client to decide. Server logs Jun 13 15:14:24 ovpn-server1[4218]: XX.XXX.XX.XX:25947 VERIFY OK: depth=1, C=TW, ST=TW, L=Taipei, O=ASUS, OU=Home/Office, CN=RT-AX88U_PRO...

You mean regarding client-connect? Can try, but the script is executed correctly. --> tried it... same result...

Yeah, sure... my bad... in clientconnect.sh I push static client IPs depending on who is actually connecting. That's basically it. Wenn I connect e.g. via mobile to my OpenVPN, I can e.g. ping local LAN clients (192.168.1.x) and vice versa, even though the server is configured as "Internet...

Anybody else witnessing that issue? LAN isolation from VPN clients is no longer working. Any idea, how I can enforce that manually in the meantime until it gets fixed? Tried to mess around with iptables already but without luck...