-
Notifications
You must be signed in to change notification settings - Fork 311
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
Update documentation for docker #1694
Comments
|
Cool! Can we also mention wireguard setup? Or wireguard is not supported in our docker images ATM? |
this should be needed only if you want to test whether your port mapping configuration works. Service itself and port mapping should be run on UDP protocol thus for production |
Also, with recent NAT changes there should be no need to run such port mapping configuration at all. Documentation should clearly state that such configuration should only be used if client has strict firewall configuration rules and wants to control all access through firewall. |
Instructions added for static port. Will update once another solution is possible. |
In docker related documentation we should describe how to specify a range of ports which we can map and use for NAT pinging. This should fix most of the cases of #1599.
Also mention in the documentation that docker support in a local network is experimental and may not work in all cases.
The text was updated successfully, but these errors were encountered: