VPN disconnected after some time

[brunix86]

Hi,

I noticed that the VPN connection is automatically disconnected after some time and I don't know why.

Before:

VPN works fine

vpn active.jpg (13.65 KiB) Viewed 3163 times

After:

VPN disconnected

vpn not active.jpg (6.76 KiB) Viewed 3163 times

Configuration:
Provider: BulletVPN
Connection Type: L2TP/IPSec

VPN config

vpn config.jpg (21.34 KiB) Viewed 3163 times

As you can see, I set the option "Reconnect when VPN connection is lost" and it doesn't work as I expected.
Another problem is that the VPN connection doesn't start automatically for each TNAS boot (start\restart).

Can someone of the TNAS support help me?
Thanks in advance.

[TMSupport]

How long does it take to disconnect automatically after successfully connecting to the VPN? Will disconnection occur every time when connecting to the VPN?

[brunix86]

How long does it take to disconnect automatically after successfully connecting to the VPN? Will disconnection occur every time when connecting to the VPN?

Hi,
I don't know how much time it takes to disconnect.
The disconnection is not related to the use of the VPN, because first the VPN works for a certain time and then, maybe after some idle time, it disconnects.
But an interesting question is: why the "Reconnect when VPN connection is lost" option doesn't work?
And why after restart of the TNAS, the VPN doesn't automatically start?
If you explain me how to catch log files, I can send you them.

Thanks

[Hardfecx]

Has that nothing to do with the stand by of the disks after installed time?
Maybe try an dyndns (duckdns is free) and try to connect via dyndns.

[brunix86]

{L_BUTTON_AT}Hardfecx

Hi,

I don't think so, because it's true that I have set 30 minutes time before standby, but it's also true that I have Plex, Docker, VirtualBox and other so many applications that use the disks, that I don't think my TNAS disks could go in standby.
I could try to deactivate the standby timer, fron 30 minutes to never.

[Hardfecx]

{L_BUTTON_AT}Hardfecx

Hi, I don't think so, because it's true that I have set 30 minutes time before standby, but it's also true that I have Plex, Docker, VirtualBox and other so many applications that use the disks, that I don't think my TNAS disks could go in standby. I could try to deactivate the standby timer, fron 30 minutes to never.

well yes that's true, I don't really understand stand it.It can't be your firewall because you get a first connection, so port forwarding is done too I think. Maby give it a try with duckdns...?

[brunix86]

{L_BUTTON_AT}Hardfecx

Hi,

Yes, and it works fine (I see the different public IP) with installed applications (eg. multimedia applications like Plex).
But at a certain time, the VPN disconnects itself with no obvious reason.
For example, now is connected for about 20 hours, but sometimes the issue happens after few hours.

What I have to expect with duckdns ?
I already used a DDNS service but I don't need it anymore.

[Hardfecx]

DuckDns was just a pourpose but if you use already DDNS you don't nee it. As you surely know, DDNS transforms your public ip to a name...

[brunix86]

{L_BUTTON_AT}Hardfecx

Hi, Ok, now it's clear and I need both DDNS (and it works) and VPN functionalities. So, I renew my initial answer to the TM support: why the "Reconnect when VPN connection is lost" option doesn't work? If this option works, when the VPN is disconnected it should automatically reconnect. And also: why the VPN doesn't start automatically for each boot of the TNAS?

[Hardfecx]

[at=brunix86 post_id=14343 time=1636640273 user_id=4205][/at]

Of course the function to get back lost a vpn connection has to work.
But I asking me, why you loose the connection? May it possible that your modem/router "restarts" or "reconnets" the DSL connection and so you get automaticly a new ip? (If yes, and I am pretty sure that is the reason, you have to work with dyndns so you can get every IP of the world but it's transform your name you have registred to it in the IP. That's why I suggested you DynDns)
Now it's the work of the support to verify why a lost connection can not be etablished (well logically because you don't have the new Ip adress your modem/router got)...