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

Docker host requires additional iptables NAT rule #16

Closed
ewrogers opened this issue May 23, 2017 · 2 comments

Comments

Projects
None yet
5 participants
@ewrogers
Copy link

commented May 23, 2017

Running mysterium-node as a Docker container will cause connected clients to be without WAN access if an additional iptables NAT rule is not specified.

Docker host should add the following NAT rule to iptables:
sudo iptables --table nat -A POSTROUTING -o eth0 -s 10.8.0.0/16 -j MASQUERADE

(Replace eth0 with your WAN interface if it differs)

The mysterium-node container should then be restarted and connected clients will now have WAN access.

@KFDCompiled

This comment has been minimized.

Copy link

commented May 23, 2017

Confirmed that this solution works for nodes behind a firewall. Make sure that there are no lingering docker rules with sudo iptables -t nat -nvL

@Waldz Waldz added this to the After ICO milestone May 29, 2017

@Waldz Waldz added the enhancement label May 29, 2017

@Nipol

This comment has been minimized.

Copy link

commented May 31, 2017

There is something else to report.
Lightsail in AWS will pass static IP incoming connections to private ip, so eth0 will only appear as private IP.
Therefore, the method described here does not apply.
In conclusion, mysterium should be able to work through techniques such as "hole punch".

If you can see it, check the my node connection.
my node on mvp

@ramzius ramzius closed this Sep 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.