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
Server cannot access Clients #211
Comments
Server is able to ping clients by default. If it isn't for you, the problem is on your side (likely client dropping inbound ICMP). Anyway this script is intended as a road-warrior kind of setup, not for internal networking. |
@Nyr : I would like to echo @saikek's comment. I am having a hard time pinging the clients as well. ps: I have not set up any firewall, iptables are flushed, I can see icmp request coming into the client but client cannot respond. Ohh and btw it has always worked fine on my mac using tunnelblick. However the above mentioned issue is present on my Linux (Ubuntu) machines |
@saikek : Incase you were not able to resolve this issue, @Nyr has answered this in Issue #190. Simply go through the script and check the line where his script sets the NAT for VPN subnet and instead, add an exception to our VPN subnet.
and enter this:
This should work. |
@Mohitsharma44 that way, you enable internal networking between clients too. You could replace Aditionally, you could avoid routing internet traffic via the VPN altogether removing that rule, if only internal networking is wanted. |
Ah great. Thanks for the tip. Since I want client-to-client communication and natting, your current script with the above iptable change works great. |
Can you add configuration option to add
FORWARD
or some other routing / iptable rules, so Server would be able to connect to clients / ping clients ?Currently clients are not visible to server.
The text was updated successfully, but these errors were encountered: