Problem: With a normal -bind (but no dedicated onion bind), automatic Tor services can forward incoming connections to the normal P2P listener, where they may be misclassified and inherit IP-based whitelist permissions.
Fix: If no dedicated onion bind exists, keep Tor control available for outbound proxy discovery but skip automatic incoming service creation and warn after authentication.
The node starts with its configured listeners (including the default onion listener when no -bind is supplied), and Tor control starts only after those listeners have been opened successfully.
Affected nodes need a concrete -bind=<addr>:<port>=onion to restore incoming Tor connections.
Wildcard onion binds are rejected at startup when -listenonion is enabled, while their classification with -listenonion=0 remains outside this change.