Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ping devices behind VPN client #42

Closed
phate82 opened this issue Dec 11, 2017 · 1 comment
Closed

Ping devices behind VPN client #42

phate82 opened this issue Dec 11, 2017 · 1 comment

Comments

@phate82
Copy link

phate82 commented Dec 11, 2017

Hi,
I started this docker container on my server. Then, I successfully connected a L2TP client (configured on a mikrotik mAP 2nD router) to the container. Now, the router running the L2TP client has three address classes (and two physical ethernet ports): one private address class (10.0.10.0/24) on the WAN interface that is connected to the horizontal wiring to get the Internet connection, one private address class (192.168.88.0/24) on the second ethernet port, and one private address 192.168.42.11 as VPN client (the VPN server has the 192.168.42.1 address). The VPN endpoints are able to ping each other and the clients on the 192.168.88.0/24 network are able to ping the VPN server endpoint (i.e. 192.168.42.1). Unfortunately, I can't ping the 192.168.88.0/24 network from the VPN server...do I have to change something on the VPN server configuration? or is this a VPN client issue?
Thanks

@phate82
Copy link
Author

phate82 commented Dec 13, 2017

I solved by sending all the traffic to the VPN client address and then forwarding (with a NAT rule) the traffic to the proper destination basing on the destination port.

@phate82 phate82 closed this as completed Dec 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant