[GH-ISSUE #64] Clients reach each other #56

Closed
opened 2026-03-02 07:11:24 +03:00 by kerem · 2 comments
Owner

Originally created by @cipherspec on GitHub (Apr 1, 2018).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/64

Thanks for this repo Dockerfile.

I can set up the VPN on all my devices, OSes ..., all connections do work perfectly. Nice one.

But, what I don't understand: is there a possiblity to make the clients reach each other? I set up routes on every client (excepting Android), using the VPNs internal gateway (in default run.sh its 192.168.42.1), and the clients get ip adresses ...42.10, ...42.11, ...42.12, but they can't ping or tcp syn each other.

Is an libreswan / ipsec configuration missing in default config? I read about the client-to-client-directive, but if I remember right, it was in openvpns configuration, not libreswan.

Any hints? Thank you very much!

Originally created by @cipherspec on GitHub (Apr 1, 2018). Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/64 Thanks for this repo Dockerfile. I can set up the VPN on all my devices, OSes ..., all connections do work perfectly. Nice one. But, what I don't understand: is there a possiblity to make the clients reach each other? I set up routes on every client (excepting Android), using the VPNs internal gateway (in default run.sh its 192.168.42.1), and the clients get ip adresses ...42.10, ...42.11, ...42.12, but they can't ping or tcp syn each other. Is an libreswan / ipsec configuration missing in default config? I read about the client-to-client-directive, but if I remember right, it was in openvpns configuration, not libreswan. Any hints? Thank you very much!
kerem closed this issue 2026-03-02 07:11:24 +03:00
Author
Owner

@hwdsl2 commented on GitHub (May 14, 2018):

@cipherspec Hello! The default VPN configuration in the Docker image does allow VPN clients to reach each other via their assigned internal VPN IPs (192.168.42.10, 192.168.42.11, etc.) The required IPTables rules are already present [1]. AFAIK there is no client-to-client directive in the Libreswan configuration.

With that said, many VPN clients such as Windows and iOS have built-in firewalls which could disallow pings and other traffic. So VPN client-to-client connections may not work reliably.

[1] https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/run.sh#L244-L249

<!-- gh-comment-id:388705883 --> @hwdsl2 commented on GitHub (May 14, 2018): @cipherspec Hello! The default VPN configuration in the Docker image does allow VPN clients to reach each other via their assigned internal VPN IPs (192.168.42.10, 192.168.42.11, etc.) The required IPTables rules are already present [1]. AFAIK there is no client-to-client directive in the Libreswan configuration. With that said, many VPN clients such as Windows and iOS have built-in firewalls which could disallow pings and other traffic. So VPN client-to-client connections may not work reliably. [1] https://github.com/hwdsl2/docker-ipsec-vpn-server/blob/master/run.sh#L244-L249
Author
Owner

@anklav24 commented on GitHub (Jun 17, 2022):

Hi, I'm facing the same problem. Have you found the solution?

<!-- gh-comment-id:1158780430 --> @anklav24 commented on GitHub (Jun 17, 2022): Hi, I'm facing the same problem. Have you found the solution?
Sign in to join this conversation.
No milestone
No project
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#56
No description provided.