[Prsym 5.3.0] p2p-tcp-port and p2p-udp-port cannot be the same port any more

[puppetninja]

Describe the bug

when running beacon chain with same p2p-tcp-port and p2p-udp-port value, there is a port binding failure

Has this worked before in a previous version?

yes, 5.1.2

🔬 Minimal Reproduction

1. run prysm 5.3.0 beacon chain with

--p2p-tcp-port=13000 --p2p-udp-port=13000

Error

please check the above attachment

Platform(s)

No response

What version of Prysm are you running? (Which release)

5.3.0

Anything else relevant (validator index / public key)?

No response

[nalepae]

The --help flag of Prysm beacon node says:

...
   --p2p-quic-port value                                The QUIC port used by libp2p. (default: 13000)
   --p2p-tcp-port value                                 The TCP port used by libp2p. (default: 13000)
   --p2p-udp-port value                                 The UDP port used by the discovery service discv5. (default: 12000)
...

By default, the port 13000 is now used for both TCB and QUIC (UDP). (It was not the case before.)

So, if you want to use --p2p-udp-port 13000 option, you have to use the --p2p-quic-port <something else than 13000> option as well.

Note: I agree the help message

   --p2p-quic-port value                                The QUIC port used by libp2p. (default: 13000)

is not crystal clear about the fact that the QUIC port is actually an UDP port.

[puppetninja]

Ah, thanks for pointing this out 👍 , was confusing about it, will close this