[Question] How hard would it be to configure this vpn server to give access to the server local network ( as it already does ) but don't route traffic outside server local network through the server ?

[iTris666]

Checklist

• [ X] I searched existing Issues, and did not find a similar enhancement request
• [X ] This enhancement request is about the IPsec VPN server Docker image, and not IPsec VPN itself
• [ X] I read the README
• [X ] I read the Important notes
• [X ] I followed instructions to configure VPN clients
• [X ] I checked IKEv1 troubleshooting, IKEv2 troubleshooting, enabled logs and checked VPN status

Describe the enhancement request [Question] How hard would it be to configure this vpn server to give access to the server local network ( as it already does ) but don't route traffic outside server local network through the server ?

I want to access my home network remotely and securely ( which this docker image provides) but I don't want all traffic from my client that have nothing to do with my home network to go through this vpn even when I'm connected to the vpn. It can be called bridge vpn or split vpn depending on the source.

Thanks a lot for this amazing docker !

[hwdsl2]

@iTris666 Hello! First, thank you for your support! The feature you mentioned is called split tunneling.

First start a Bash shell inside the container, then refer to the steps in the split tunneling section in advanced usage. When finished, exit the container and run docker restart ipsec-vpn-server.

Note that when editing /etc/ipsec.conf, you should also edit the corresponding section in /opt/src/run.sh, so that the changes can persist after a container restart.