TID: Mystic BBS 1.12 A48
MSGID: 1:129/215 8d8b0eda
REPLY: 1:229/664.1 80435ce2
TZUTC: -0500
 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> 
 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)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 120/340 616 123/10
SEEN-BY: 123/131 124/5016 129/215 305 153/757 7715 154/10 30 40 50
SEEN-BY: 154/700 203/0 218/700 220/90 221/0 1 6 226/18 30 70 227/114
SEEN-BY: 227/201 229/110 111 112 113 114 206 275 307 310 317 400 424
SEEN-BY: 229/426 428 452 470 550 664 700 240/1120 5832 261/38 266/512
SEEN-BY: 280/464 5003 282/1038 292/854 8125 301/1 317/3 320/219 322/757
SEEN-BY: 335/364 341/66 234 342/200 396/45 460/58 633/280 712/848
SEEN-BY: 770/1 2320/105 3634/12 5020/1042
PATH: 129/215 154/10 280/464 292/854 229/426