Hello,
Our users facing problem when using pritunl. We implemented split tunnel. private network via pritunl and public network via local traffic(isp)
But everytime user access public network for some minutes and switch to access private network, the pritunl cant handle it. while the pritunl client sill shown connected.
We have configure user session timeout to 43200 seconds(12 hours), and uncheck enable client reconnect on server side and client side.
How to fix this, because its happened on our production environment?
First verify it isn’t DNS by checking if an IP address on the private network can be accessed. Also follow the update OpenVPN documentation to update OpenVPN on the server. Older releases have an issue causing routing to fail about a minute after connection.
Switching the server to TCP and setting the connection MTU can also fix some issues. If this does fix the issue refer to the client debugging documentation for more information on debugging MTU issues.
Thanks for your response @zach,
By the way I cant figure out about the dns one.
In the beginning after vpn connected all the route worked normally(private and public). The issue wiil be come when we didnt access private service for more than 15 minutes.
From your explanation I think setting up mtu is the most viable option, then switching server and last updating the open, right?
I have an update regarding this issue.
Ive try to make lower mtu on server but I got warning on server log.
’
type or paste code herWARNING: 'link-mtu' is used inconsistently, local='link-mtu 1293', remote='link-mtu 1535'
WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1258', remote='tun-mtu 1500e
Additional information.
After around 20 minutes idle and pritunl still connected, my network doesnt work for public and private
;; connection timed out; no servers could be reached
