docs: clarify ipv6 details in networking page (#8368)

**Motivation**

After resolving issues with the ipv6 dual stack port bug in v1.34.1, it
was noted that we should make it clear our default p2p port for both
IPv4 and IPv6 is now the same at port `9000`.

**Description**

When we introduced IPv6 support in #5758 , we used to default the port
of `9090`. When supporting dual stack option on the same port via #8190
, we should make it clear in documentation this is now by default also
on port `9000`.

Author: philknows

docs/pages/run/beacon-management/networking.md

@@ -41,12 +41,18 @@ The primary purpose of ENRs is to facilitate node discovery and connectivity in
 
 Note that bootnodes are announced via ENR.
 
-Lodestar prints out its own ENR on startup, the logs will show something similar to the following
+Lodestar prints out its own ENR on startup, the logs will show something similar to the following for IPv4 nodes:
 
 ```txt
 info: discv5 worker started peerId=16Uiu...t9LQ3, initialENR=enr:-Iu4QGE...WRwgiMo, bindAddr4=/ip4/0.0.0.0/udp/9000
 ```
 
+Or similar to the following for IPv6 dual-stack nodes (when enabled):
+
+```txt
+info: discv5 worker started peerId=16Uiu...t9LQ3, initialENR=enr:-Iu4QGE...WRwgiMo, bindAddr4=/ip4/0.0.0.0/udp/9000, bindAddr6=/ip6/::/udp/9000
+```
+
 Alternatively, the ENR can also be retrieved from the beacon node API by querying the [getNetworkIdentity](https://ethereum.github.io/beacon-APIs/#/Node/getNetworkIdentity) endpoint.
 
 [ENR Viewer](https://enr-viewer.com/) provides a simple and convenient option to decode and inspect ENRs.
@@ -80,8 +86,7 @@ If your setup is behind a firewall there are a few ports that will need to be op
 Ports that must be opened:
 
 - 30303/TCP+UDP - Execution layer P2P communication port
-- 9000/TCP+UDP - Beacon node IPv4 P2P communication port
-- 9090/TCP+UDP - Beacon node IPv6 P2P communication port
+- 9000/TCP+UDP - Beacon node IPv4 and IPv6 P2P communication port
 
 Ports that must be protected: