SocketConnectHost does not support IP6 addresses about quickfixn HOT 5 OPEN

This writeup is terrible.

What we want to verify is that users can specify IPv6-format addresses for SocketConnectHost and SocketAcceptHost, and have their apps connect properly.

I'm not sure how "localhost" factors into this, but the engine should be able to handle it in an appropriate fashion.

from quickfixn.

Pull request #67 not accepted. Tests requested.

from quickfixn.

localhost factors into this, because on IPv6 aware machines, localhost resolves to ::1 instead of 127.0.0.1. This is particularly apparent when using stunnel locally to encrypt connections as SocketConnectHost is normally set to localhost to tunnel the connection elsewhere.

QuickFIX allowed "localhost" in the configuration, therefore all QuickFIX config files referencing this will break with QuickFIX/n.

from quickfixn.

Anyone looking at this one? It's a bit of a pain because every time any of our clients upgrade, they get in touch with us to say their config no longer works. E.g. they get an error like so:

Connecting to ::1 on port 12345
Connection failed: An address incompatible with the requested protocol was used [::1]:12345

We then have to tell them to change any references to Localhost in their config explicitly to the IPv4 address.

from quickfixn.

Literally haven't thought about it for a year. No one was demanding it, so I have not prioritized it.

I'd love to get it knocked out. It would probably be easy for someone with the knowledge of IPv6/C# specifics, but I'm not that guy right now.

from quickfixn.