From 1573261512793b2170e06d14e3e9300ef6183a01 Mon Sep 17 00:00:00 2001 From: mehmetkr-31 Date: Sun, 10 May 2026 20:13:04 +0300 Subject: [PATCH] fix: add HOST_IP support to reth entrypoint The geth entrypoint already supports HOST_IP via --nat=extip, and the nethermind entrypoint was recently updated to use --Network.ExternalIp. However, the reth entrypoint ignores HOST_IP entirely, leaving reth operators with poor peer discovery when running behind NAT. Add the same conditional logic to pass --nat=extip when HOST_IP is set, completing parity across all three supported execution clients. --- execution-entrypoint | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/execution-entrypoint b/execution-entrypoint index cea226016..33505b0eb 100755 --- a/execution-entrypoint +++ b/execution-entrypoint @@ -127,6 +127,10 @@ if [[ "$RETH_HISTORICAL_PROOFS" == "true" && -n "$RETH_HISTORICAL_PROOFS_STORAGE --proofs-history.storage-path=$RETH_HISTORICAL_PROOFS_STORAGE_PATH fi +if [ "${HOST_IP:+x}" = x ]; then + ADDITIONAL_ARGS="$ADDITIONAL_ARGS --nat=extip:$HOST_IP" +fi + mkdir -p "$RETH_DATA_DIR" echo "Starting reth with additional args: $ADDITIONAL_ARGS" echo "$BASE_NODE_L2_ENGINE_AUTH_RAW" > "$BASE_NODE_L2_ENGINE_AUTH"