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

[GH-ISSUE #470] Connect container to multiple interfaces #440

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

Originally created by @UnBonWhisky on GitHub (Mar 15, 2025).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/470

Checklist

Describe the enhancement request
Would it be possible to connect the container to multiple interfaces ?

Is your enhancement request related to a problem? Please describe.
Currently, when connecting the container to 2 or 3 networks, I am unable to ping the 2nd and 3rd interfaces (eth1 and eth2). I would like to contact all the networks my container is in

Additional context
Add any other context about the enhancement request here.

Originally created by @UnBonWhisky on GitHub (Mar 15, 2025). Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/470 **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) - [ ] 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** Would it be possible to connect the container to multiple interfaces ? **Is your enhancement request related to a problem? Please describe.** Currently, when connecting the container to 2 or 3 networks, I am unable to ping the 2nd and 3rd interfaces (eth1 and eth2). I would like to contact all the networks my container is in **Additional context** Add any other context about the enhancement request here.
kerem closed this issue 2026-03-02 08:18:58 +03:00
kerem commented 2026-03-02 08:18:58 +03:00
Author
Owner
Copy link

@hwdsl2 commented on GitHub (Mar 15, 2025):

@UnBonWhisky Hello! This use case is not currently supported in this project. However, you may be able to achieve this using the following steps (not tested).

First open a bash shell inside the container:

https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/docs/advanced-usage.md#bash-shell-inside-container

Next, add IPTables rules to allow traffic to additional network interfaces such as eth1. See:

https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/advanced-usage.md#access-vpn-servers-subnet

Please let us know in this issue if you are able to successfully achieve your use case.

<!-- gh-comment-id:2726747848 --> @hwdsl2 commented on GitHub (Mar 15, 2025): @UnBonWhisky Hello! This use case is not currently supported in this project. However, you may be able to achieve this using the following steps (not tested). First open a bash shell inside the container: https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/docs/advanced-usage.md#bash-shell-inside-container Next, add IPTables rules to allow traffic to additional network interfaces such as eth1. See: https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/advanced-usage.md#access-vpn-servers-subnet Please let us know in this issue if you are able to successfully achieve your use case.
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#440
No description provided.