AR300M wireguard unstable on latest firmware v3.24

ongkang · 2019-08-11T01:06:52.766Z

Hi, I have been using wireguard client on firmware v3.19 and work really well (uptime more than a week). But recently I updated to v3.24 (and also beta v3.26) and I got disconnected with unsuccessful automatic retry within less than 12 hours. The only solution is to stop automatic retry and then manually reconnect.
Unfortunately I could not get the logs about when this disconnect happened. The log itself was already full with error for stubby.
This v3.24 is great with additional MTU option, which I need the most since GCP wireguard server limit the MTU, and also VPN policy that looks great. Please help me to stick with this new version

kyson-lok · 2019-08-12T07:54:24.599Z

Which WireGuard Server are you using for? Setup by yourself or use 3rd party VPN provider?

ongkang · 2019-08-18T00:05:05.501Z

I setup WireGuard Server using Google cloud platform (gcp) by myself. I am aware about low mtu from it (1380) but it could be altered using mtu setting in router (1360). That’s how it used to work in firmware v3.19

kyson-lok · 2019-08-19T04:24:02.200Z

You can upgrade to latest testing firmware, which support setting mtu on webUI.

ongkang · 2019-08-27T12:22:16.494Z

Yes, I am using that now. MTU setting could be added in config file too in previous version so I don’t think it fix the issue.
For temporary solution, I created watchdog script that will restart wireguard if it got disconnected.

And by the way, the vpn policy is working very well with mac filter, even when the wireguard is down.

alzhao · 2019-08-28T01:38:48.353Z

ongkang:

And by the way, the vpn policy is working very well with mac filter, even when the wireguard is down.

I am glad to hear that the vpn policy works for you!