Intermittent issues with Travel Router to VPN server back home

Technical Support for Routers VPN, DNS, Leaks
1

Hi
I have what was a working travel router with VPN working back home in New Zealand, showing my IP address correctly in Australia.

These fix upon restarting the home (server) router and VPN server, which I always have to ask a friend to do - so it's not ideal!

At home setup
Brume VPN server connected via ethernet to main router
DDNS enabled
DHCP reservation enabled

Overseas - where I am now
Slate AX travel router, firmware up to date
DDNS Enable and config file working
DDNS enabled

At variable timeframes, sometimes 2 weeks, sometimes 3 days, and now it seems to be more often than not (every few days), the VPN goes down. I tested another VPN from a provider on my SlateAX and switched to that config - it's working fine. And, unfortunately, it shows up I am using a VPN which is NOT good for work!

The logs today say:
Sun Nov 3 09:09:20 2024 user.notice firewall: Reloading firewall due to ifup of wgclient (wgclient)
Sun Nov 3 09:10:27 2024 daemon.notice netifd: Network device 'wgclient' link is down
Sun Nov 3 09:10:27 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Sun Nov 3 09:10:27 2024 daemon.notice netifd: Interface 'wgclient' is now down
Sun Nov 3 09:10:27 2024 daemon.notice netifd: Interface 'wgclient' is setting up now

On other occasions it has been:

Thu Oct 10 08:14:56 2024 daemon.notice netifd: wgclient (13777): Name does not resolve: `xxxxxxxxx.glddns.com:51820'

I am not changing anything on my side.
I notice sometimes this occurs when the public IP address of my ISP changes, and other times it doesn't change, and the error occurs.

As I said, it always needs a restart of my main router and Brume - I can't keep asking my friend to do this.

Any tips or guidance?

2

May I know when the VPN connection drop/down, if the public IP which your primary router and xxxxxx.glddns.com can ping?

Probably the public IP has been changed, glddns has to take a few minutes to check and then report/update when the public IP is changed.

4

I can test when it’s next down
But essentially it goes down until the VPN and router reboot. So it’s not a few minutes it’s “until my friend can reboot the router and VPN (Brume)”. Waiting a day or two doesn’t help.

5

I use older gl.inet ar300m routers at friend's and families' places as VPN servers. I do a daily reboot, using cron, as even a small memory leak builds up over time. I have not had any unexpected down time in years of using these.

The ar300m is not the fastest VPN server, but they are small, low power, reliable and cheap.

6

Maybe I can try the same.
How does someone run a cron job on a vpn?

Meanwhile, I have the latest high powered slate AX and this happens :joy:

7

Sorry, I also have the latest high powered Brume VPN too and this happens :joy:

8

See:

9

Thanks but I strongly think the issue is on the VPN side so I’ll set a cron job for the VPN not the router

10

Here your reference, choose which the command for VPN service is using to instead of the system reboot
ifup wgclient
ifup wgserver
ifup ovpnclient
ifup ovpnserver

Only 'ifup' is needed to bring the service restart, does not need the 'ifdown'.

1 Like