mirror of
https://github.com/hwdsl2/docker-ipsec-vpn-server.git
synced 2026-04-26 01:55:53 +03:00
[GH-ISSUE #12] How to allow clients to connect to each other? #12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @013231 on GitHub (Oct 11, 2016).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/12
I've set up a vpn server and now every client is connected to the server. The connections between clients and server is perfect, but these clients can't communicate with each other. How to solve this problem?
@hwdsl2 commented on GitHub (Oct 11, 2016):
@013231 If the VPN clients are connected to the server via IPsec/L2TP, they should be assigned IPs within the VPN subnet 192.168.42.0/24. For example, the VPN server is at 192.168.42.1, and VPN clients are at 192.168.42.10, 192.168.42.11, 192.168.42.12, etc. In the default configuration, VPN clients can communicate with each other using the IP addresses as mentioned above.
@013231 commented on GitHub (Oct 11, 2016):
@hwdsl2 Thanks. I know the subnet ips, but these clients really cannot communicate with each other.
ping 192.168.42.1(ping server from client0):ping 192.168.42.1(ping server from client1):ping 192.168.42.10(ping client0 from server):ping 192.168.42.11(ping client1 from server):ping 192.168.42.11(ping client1 from client0):And I found the solution:
http://unix.stackexchange.com/questions/110436/pptp-allow-remote-clients-to-communicate-with-each-other
@hwdsl2 commented on GitHub (Oct 11, 2016):
@013231 Thanks for the update, and happy to hear you got it working. I still think that the IPTables rules in run.sh should take care of this. See run.sh#L210-L224
@013231 commented on GitHub (Oct 11, 2016):
@hwdsl2 Sorry, I use an old image without run.sh#L216 😓
@hwdsl2 commented on GitHub (Oct 11, 2016):
@013231 Ah I see where the problem is. I suggest that you update to the latest image using
docker pull hwdsl2/ipsec-vpn-server, and deploy a new container using instructions from the README. You may need to stop or destroy the old container before this step.