Can't connect customize testnet network

[avenbreaks]

Describe the bug

we are unable to use reth on the testnet network the customization in the logs does not show such as connected enodes and peers.

Steps to reproduce

#!/bin/bash

nohup reth node \
        --datadir=/home/ubuntu/testnet/execution \
        --chain=/home/ubuntu/testnet/custom_config_data/genesis.json \
        --http \
        --http.port 8545 \
        --http.addr 127.0.0.1 \
        --http.corsdomain=* \
        --http.api=admin,debug,eth,net,trace,txpool,web3,rpc,reth,ots \
        --ws \
        --ws.addr 127.0.0.1 \
        --ws.port 8546 \
        --ws.api=debug,eth,net,trace,txpool,web3,rpc,reth,ots \
        --ws.origins=* \
        --nat extip:18.194.225.136 \
        --identity=reth-paradigm \
        --full \
        --authrpc.port 8551 \
        --authrpc.addr 127.0.0.1 \
        --authrpc.jwtsecret=/home/ubuntu/testnet/custom_config_data/jwtsecret \
        --metrics=127.0.0.1:6060 \
        --port 30303 \
        --discovery.port 30303 \
        --bootnodes="enode://7fb8b8c922c034de8e08c83ab332c944d15ee2283aa22ba4554fc2fe217688d25bb3629613a8e981b3aaa8c15d93b17d07da3289731637b4c87530492e52ba5f@159.223.32.178:30303" \
        > /home/ubuntu/testnet/logs/reth.log &

Node logs

�[2m2023-10-30T13:54:30.338287Z�[0m �[32m INFO�[0m �[2mreth::cli�[0m�[2m:�[0m reth 0.1.0-alpha.10 (1b16d80) starting
�[2m2023-10-30T13:54:30.338475Z�[0m �[32m INFO�[0m �[2mreth::cli�[0m�[2m:�[0m Configuration loaded �[3mpath�[0m�[2m=�[0m"/home/ubuntu/testnet/execution/reth.toml"
�[2m2023-10-30T13:54:30.338492Z�[0m �[32m INFO�[0m �[2mreth::cli�[0m�[2m:�[0m Opening database �[3mpath�[0m�[2m=�[0m"/home/ubuntu/testnet/execution/db"
�[2m2023-10-30T13:54:30.344349Z�[0m �[32m INFO�[0m �[2mreth::cli�[0m�[2m:�[0m Database opened
�[2m2023-10-30T13:54:30.344393Z�[0m �[32m INFO�[0m �[2mreth::cli�[0m�[2m:�[0m Starting metrics endpoint �[3maddr�[0m�[2m=�[0m127.0.0.1:6060
�[2m2023-10-30T13:54:30.345463Z�[0m �[32m INFO�[0m �[2mreth::cli�[0m�[2m:�[0m Pre-merge hard forks (block based):
- Homestead                        @0
- Tangerine                        @0
- SpuriousDragon                   @0
- Byzantium                        @0
- Constantinople                   @0
- Petersburg                       @0
- Istanbul                         @0
- Berlin                           @0
- London                           @0
Merge hard forks:
- Paris                            @0 (network is known to be merged)

Post-merge hard forks (timestamp based):
- Shanghai                         @1698332372
- Cancun                           @1706012372

Platform(s)

Linux (x86)

What version/commit are you on?

reth Version: 0.1.0-alpha.10

What database version are you on?

Current database version: 1
Local database is uninitialized

What type of node are you running?

Full via --full flag

What prune config do you use, if any?

No response

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

• I agree to follow the Code of Conduct

[mattsse]

I see,

we use --bootnodes for P2P discovery, and they're not emitted to the pool of available peers, which would explain why you don't see connection attempts to this peer
The reasoning here was that the discovery bootnodes are usually full anyway, but perhaps we should rethink that again.

could you try --trusted-peers ?

[avenbreaks]

I see,

we use --bootnodes for P2P discovery, and they're not emitted to the pool of available peers, which would explain why you don't see connection attempts to this peer The reasoning here was that the discovery bootnodes are usually full anyway, but perhaps we should rethink that again.

could you try --trusted-peers ?

work with --bootnodes and --trusted-peers. closed