JH> Being able to force poll everything with IPv4 with a -4 flag would make
JH> things easier than going into ./mystic -cfg to switch the node to IPv4
JH> and then running ./mis poll
JH> That being said, if an IPv6 poll doesn't work, isn't it supposed to fall
JH> back to IPv4? I've not seen that be the case.
Its supposed to work that way which would mean the -4 and -6 would not be all
that useful. But...
The fallback from IPV6 to IPV4 is only working if the DNS doesn't resolve an
IPV6 address. If it resolves IPV6 and IPV4, it is not falling back to IPV4
properly on a failed IPV6 connect attempt.
It *is* coded to fallback/function like "Happy Eyeballs" as Alisha mentioned
earlier when set to "Default IPV6" or "IPV6+IPV4", but its broken. Not
surprising since I coded IPV6 support way back in day without having IPV6
myself.
For now I have changed the nodelist-lookup-based connections to use IPV4 in the
latest build until I can figure out what is going wrong. With any luck I'll get
some time to fix it up this weekend.
... Everyone smiles in the same language.
--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)
|
