starred/docker-ipsec-vpn-server
1
0
Fork 0
mirror of https://github.com/hwdsl2/docker-ipsec-vpn-server.git synced 2026-04-28 11:05:49 +03:00
Code Issues Projects Releases Packages Wiki Activity

[GH-ISSUE #417] [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 ? #390

New issue
Closed
opened 2026-03-02 08:01:50 +03:00 by kerem · 1 comment
kerem commented 2026-03-02 08:01:50 +03:00
Owner
Copy link

Originally created by @iTris666 on GitHub (Feb 20, 2024).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/417

Checklist

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 !

Originally created by @iTris666 on GitHub (Feb 20, 2024). Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/417 **Checklist** - [ X] I searched existing [Issues](https://github.com/hwdsl2/docker-ipsec-vpn-server/issues?q=is%3Aissue), 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](https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/README.md) - [X ] I read the [Important notes](https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/README.md#important-notes) - [X ] I followed instructions to [configure VPN clients](https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/README.md#next-steps) - [X ] I checked [IKEv1 troubleshooting](https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#ikev1-troubleshooting), [IKEv2 troubleshooting](https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/ikev2-howto.md#ikev2-troubleshooting), [enabled logs](https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/docs/advanced-usage.md#enable-libreswan-logs) and checked [VPN status](https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#check-logs-and-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 !
kerem closed this issue 2026-03-02 08:01:50 +03:00
kerem commented 2026-03-02 08:18:37 +03:00
Author
Owner
Copy link

@hwdsl2 commented on GitHub (Feb 20, 2024):

@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.

<!-- gh-comment-id:1955249391 --> @hwdsl2 commented on GitHub (Feb 20, 2024): @iTris666 Hello! First, thank you for your support! The feature you mentioned is called split tunneling. First [start a Bash shell inside the container](https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/docs/advanced-usage.md#bash-shell-inside-container), then refer to the steps in the [split tunneling](https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/advanced-usage.md#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.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
bug

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question
No labels
bug
pull-request
question
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-ipsec-vpn-server#390
No description provided.