-
Notifications
You must be signed in to change notification settings - Fork 78
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
Add NAT support. #270
Add NAT support. #270
Conversation
…igners. Signed-off-by: Byron Gravenorst <[email protected]>
Signed-off-by: Byron Gravenorst <[email protected]>
Signed-off-by: Byron Gravenorst <[email protected]>
Signed-off-by: Byron Gravenorst <[email protected]>
…to bgravenorst-TEKU-194
Signed-off-by: bgravenorst <[email protected]>
Signed-off-by: bgravenorst <[email protected]>
## None | ||
|
||
Specify `NONE` to explicitly configure the external IP address and ports advertised using | ||
[`--p2p-host`](../../Reference/CLI/CLI-Syntax.md#p2p-host) and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So in teku, manual configuration would be set using
--p2p-advertised-ip
--p2p-advertised-port
and the advertised port can differ from --p2p-port
.
For example if you need port 9001 on firewall, but 9000 on teku box, then you'd set advertised port as 9001, and manually configure your firewall to forward 9001 -> 9000 on the teku machine (udp and tcp)
discovery takes care of --p2p-host
, and teku doesnt offer that configuration option at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I also updated the --p2p-advertised-port
description using your example. Hope I understood that correctly.
Signed-off-by: bgravenorst <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Pull Request Description
Add instructions to configure NAT via UPnP.
Fixed Issue(s)
Fixes #246