Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Description of bug

We host our nodes on-demand and recently we received netscan abuse message from server provider we use.

We checked that we have --no-private-ip and --no-mdns enabled and there is no other software that may cause such behavior, but node makes P2P requests to 10/8 networks somehow (RFC-1918).

Do these arguments work correctly?

Steps to reproduce

1. Prerequisites:
   a. Debian Bookworm host OS
   b. Docker
   c. netstat installed (apt update && apt install net-tools -y)
2. Launch a node:

docker run --rm parity/polkadot:v1.18.4 \
--chain=kusama \
--database=paritydb \
--base-path=/polkadot/.local/share/polkadot/chains/ \
--name=test-node \
--pruning=5000 \
--blocks-pruning=archive \
--unsafe-rpc-external \
--rpc-port=9933 \
--out-peers=100 \
--in-peers=100 \
--in-peers-light=100 \
--prometheus-port=9093 \
--rpc-max-connections=100000 \
--no-private-ip \
--no-mdns \
--port=30333

3. Execute netstat -nputw | grep -E "10\.|\(172\.16\|192\.168\)" to check outgoing connections to RFC-1918 networks