docs: update networking page #6289
Conversation
nflaig
force-pushed
the
nflaig/update-networking-md
branch
from
d2670de
to
a0591e7
Compare
nflaig
force-pushed
the
nflaig/update-networking-md
branch
from
a0591e7
to
9fe07d8
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
| - 13000/TCP - Prysm P2P communication port | ||
| - 12000/UDP - Prysm P2P communication port |
There was a problem hiding this comment.
These should not be removed or lodestar will have issue p2p communicating with Prysm. I get that these are Lodestar docs but we communicate with Prysm
https://docs.prylabs.network/docs/prysm-usage/p2p-host-ip#configure-your-firewall
There was a problem hiding this comment.
Perhaps they go in an "optional" section with a note so people know the issue exists.
There was a problem hiding this comment.
lodestar will have issue p2p communicating with Prysm
This only concerns inbound ports, not outbound. I already mentioned that in the PR description, if you start speculating on what ports other nodes in the network are running on, you are fighting a losing battle.
Just an example, on dappnode Lodestar p2p port is configured to use 9512, same goes for other clients, they don't use default ports.
Maybe we should highlight that it is important to not block any outbound ports, but I felt like this is unnecessary as nobody does this.
There was a problem hiding this comment.
OK makes sense. Maybe we can add a note in another PR that these are the defaults and that there are some extenuating circumstances that do not fall under these rules
There was a problem hiding this comment.
Noticed in the prysm docs you linked above that they state to allow outbound traffic from any port
This might be something to consider but from my experience this is not an issue as there is no guide that I know that instructions users to block outbound traffic.
Co-authored-by: Matthew Keil <me@matthewkeil.com>
* docs: update networking page * Update wordlist * Update port description * must instead of should * Apply feedback Co-authored-by: Matthew Keil <me@matthewkeil.com> * Why on startup, who cares * Add log exmaple --------- Co-authored-by: Matthew Keil <me@matthewkeil.com>
|
🎉 This PR is included in v1.15.0 🎉 |
* docs: update networking page * Update wordlist * Update port description * must instead of should * Apply feedback Co-authored-by: Matthew Keil <me@matthewkeil.com> * Why on startup, who cares * Add log exmaple --------- Co-authored-by: Matthew Keil <me@matthewkeil.com>
Motivation
There were several users already that asked about how to retrieve their ENR, hence i think it makes sense to explicitly mention this in our docs.
Also simplified ports a little bit, I think it's better to only talk about protecting incoming ports as users should not be concerned about outgoing ports, there is no reason to block any of those and if people do, they probably have a good reason for it and know what they are doing.
There is also no point in listing Prysm ports, those were only about outbound ports and there are plenty of setups that change the default 9000 p2p port to something else, e.g. rocketpool uses 9001. Listing them all does not make sense.
Description