Correct. But that initial connection will work and the client will work, it just won’t have connections to multiple nodes.
I didn’t say it’s optimal, but this is the best way I can see that doesn’t break things more than they are now, and does give an improvement because you can pick which ports shows up in peers. Deprecating helps nothing for existing releases. We can’t/shouldn’t remove the feature in existing releases. > On Feb 7, 2024, at 8:02 AM, Abe Ratnofsky <a...@aber.io> wrote: > > If dual-native-port is enabled, a client is connecting unencrypted to the > non-SSL port, and "advertise-native-port=ssl" (name pending) is enabled, then > when that client fetches peers it will get the SSL ports, right? If the > client doesn't support SSL, then those subsequent connections will fail. An > operator would have to set "advertise-native-port=ssl" and override the port > options in all clients, which isn't feasible.
