feat(l1): add CLI flag to specify P2P listening address

[MegaRedHand]

Motivation

Description

This PR adds a flag to set the listening address for P2P.

[github-actions]

Lines of code report

Total lines added: 8
Total lines removed: 0
Total lines changed: 8

Detailed view

+--------------------------+-------+------+
| File                     | Lines | Diff |
+--------------------------+-------+------+
| ethrex/cmd/ethrex/cli.rs | 768   | +8   |
+--------------------------+-------+------+

[Copilot]

Pull Request Overview

This PR adds a new CLI flag --p2p.addr to allow users to specify the P2P listening address for the node, providing more control over network configuration. When not specified, the node continues to auto-detect the local IP address as before.

Key changes:

• Added optional --p2p.addr CLI parameter for specifying the P2P listening address
• Refactored P2P node initialization to use the provided address or fall back to auto-detection
• Updated help text for consistency across P2P-related options

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
cmd/ethrex/cli.rs	Adds new optional p2p_addr field to Options struct with CLI argument definition
cmd/ethrex/initializers.rs	Updates get_local_p2p_node to use the new CLI option, simplifying socket address parsing
docs/CLI.md	Documents the new --p2p.addr option in the CLI reference

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[MegaRedHand]

This option was moved, but wasn't removed from here.

[MegaRedHand]

Some options weren't updated since they're not checked in the CI

[MegaRedHand]

I'm getting some errors:

2025-11-14T16:20:29.118061Z ERROR Error sending message sent="Ping" to=0xd860a01f9722d78051619d1e2351aba3f43f943f6f00718d1b9baa4101932a1f5011f16bb2b1bb35db20d6fe28fa0bf09636d26a87d31de9ec6203eeedb1f666 err=IoError(Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" })
2025-11-14T16:20:29.118275Z ERROR Error sending message sent="Ping" to=0x22a8232c3abc76a16ae9d6c3b164f98775fe226f0917b0ca871128a74a8e9630b458460865bab457221f1d448dd9791d24c4e5d88786180ac185df813a68d4de err=IoError(Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" })
2025-11-14T16:20:29.118409Z ERROR Error sending message sent="Ping" to=0x2b252ab6a1d0f971d9722cb839a42cb81db019ba44c08754628ab4a823487071b5695317c8ccd085219c3a03af063495b2f1da8d18218da2d6a82981b45e6ffc err=IoError(Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" })
2025-11-14T16:20:29.118537Z ERROR Error sending message sent="Ping" to=0x4aeb4ab6c14b23e2c4cfdce879c04b0748a20d8e9b59e25ded2a08143e265c6c25936e74cbc8e641e3312ca288673d91f2f93f8e277de3cfa444ecdaaf982052 err=IoError(Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" })
2025-11-14T16:20:29.118596Z  INFO Global allocator: jemalloc (tikv-jemallocator)
2025-11-14T16:20:29.118687Z ERROR Error sending message sending="FindNode" addr=18.138.108.67:30303 err=Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }
2025-11-14T16:20:29.220044Z ERROR Error sending message sending="FindNode" addr=157.90.35.166:30303 err=Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }
2025-11-14T16:20:29.321436Z ERROR Error sending message sending="FindNode" addr=3.209.45.79:30303 err=Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }
2025-11-14T16:20:29.422591Z ERROR Error sending message sending="FindNode" addr=65.108.70.101:30303 err=Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }

But node still syncs. I think we can fix those in a later PR.

Let's address this in another PR, but I think the main problem is bootnodes use IPv4 addresses (the ones in the error messages), so we need some way to translate those.