Hybrid VPN connected but not working

[Netduma Fraser]

Did they understand what the logs were for, just to diagnose the connection issues and not for recording internet traffic? A strict no-logs policy sounds like the latter. 

It only supports OpenVPN, our own routers on DumaOS 4 support Wireguard also. Right okay maybe that has something to do with it, as if the connection takes too long to establish or has a delay during then the timeout may apply as the server hasn't responded when we would expect, this makes sense given the distance between you and the server. UDP might work better, you don't need to combine configs, TCP would still be covered by connecting to the VPN using UDP so give that a try.

What you could do is attempt to extend the timeout settings through the config by adding these lines to the config:

• connect-retry n (change n to be the number of seconds to wait between connection retries the default is 5 so try 10)
• connect-timeout n (change n to number of seconds before it considers there to be a timeout the OpenVPN default is 10 (which isn't long given your distance) so try higher) 
• connect-retry-max n (change n to be the number of retries of the connection attempt. The default is supposedly infinite but I'd set this manually as we can't be sure if that is happening)

Do throw in that syslog line as well just in case it provides more information about how these lines are doing.

There is really no other information I can use to help - you could grab the main log from the System Information page - perhaps that might show something if the cause is router based but I wouldn't count on it.

[dissonant]

Ok, well nothing I tried works.  Entering any new configs, adding those additional lines to the config or trying UDP do not seem to do anything as I don't think that the router connecting to the VPN is the issue.  I've seen connection issues in the past and they are indicated on the hVPN screen.  I think its an issue with how the router then chooses which hosts to put behind the VPN.  I guess I'll just have to stop using this feature, unless you have any other ways to troubleshoot this in the future.

[Netduma Fraser]

That's a shame, I'm not sure if it's available but the only other option that might be still available is setting the DNS on HVPN, it may help to keep the connection alive. Otherwise no unfortunately not, if it was the HVPN on the R3 (as we've re-made the feature) it may be easier for us to diagnose/make changes for a future version. 

[dissonant]

Thanks for explaining that this is an older implementation that is no longer relevant for future models...  Makes sense why fixing a problem in your old implementation of the feature isn't desirable.  I did notice that the downloads through the hVPN when it was working seemed to be limited to around 600kBps where I've noticed speeds of up to 6-7 MBps when i use the VPN app running on Windows.  You think that was due to processing power within the router being limited, comparatively speaking?  I liked the router hVPN mostly because the windows app seems to use CPU clock time even when not connected.

[Netduma Fraser]

14 minutes ago, dissonant said:

Thanks for explaining that this is an older implementation that is no longer relevant for future models...  Makes sense why fixing a problem in your old implementation of the feature isn't desirable.  I did notice that the downloads through the hVPN when it was working seemed to be limited to around 600kBps where I've noticed speeds of up to 6-7 MBps when i use the VPN app running on Windows.  You think that was due to processing power within the router being limited, comparatively speaking?  I liked the router hVPN mostly because the windows app seems to use CPU clock time even when not connected.

Yes it is a hardware limitation in that regard, it's a similar limitation on the R3 but that's why we implemented Wireguard so you can hit around 100Mbps through it

[dissonant]

100Mbps would be acceptable, maybe i'll look into the R3 or other routers that will implement dumaOS 4.  have you guys ever thought of broadcasting an additional SSID that you could have behind the VPN?  i think that its a little clunky going into the router interface to either add or remove devices so having a separate SSID similar to how you have guest networks would be a nice feature (and also you wouldn't have to give other people the admin password to the router)

[Netduma Fraser]

That's a good idea, I'll add it to the list, thanks for the suggestion!