Hey folks,
I'm using a windows client to connect to my softether vpn server. The server is set to hand out private DHCP IPs and enable NAT.
After exactly 60 seconds I can no longer ping google but the VPN connection still stays up. Pings come back after 60 seconds. rinse and repeat.
If I edit the UDP session timeout to 10 mins it times out exactly 10 mins later.
While this is happening I have a VNC window open to a remote server and that also disconnects. Since the VNC session is up i don't believe I am "idle".
Why is this timeout setting doing this? Is it safe to set it to 24 hours as a hack-fix...
Virtual NAT timeout setting
-
- Posts: 3
- Joined: Wed Mar 01, 2017 7:47 pm
Re: Virtual NAT timeout setting
So I updated to 4.22 Build 9634 Beta from the latest RTM version and I think the problem went away.
Known bug?
Known bug?
-
- Posts: 336
- Joined: Sat Aug 15, 2015 7:41 pm
Re: Virtual NAT timeout setting
I'd say no. Not a known bug
But anyway 4.22 and source code checkout are very stable compared to earlier versions
But anyway 4.22 and source code checkout are very stable compared to earlier versions
-
- Posts: 3
- Joined: Wed Mar 01, 2017 7:47 pm
Re: Virtual NAT timeout setting
Still had issues. Seems like the built-in virtual NAT is buggy for my setup.
My solution was to install a dhcp server on the host box, NAT rule with iptables and created a TAP device to bridge the softether network into it. Works like a charm with no issues.
My solution was to install a dhcp server on the host box, NAT rule with iptables and created a TAP device to bridge the softether network into it. Works like a charm with no issues.