MSGID: 2:240/1120.29 45902a06
CHRS: CP850 2
TZUTC: 0100
REPLY: 2:280/5555 6227e2bb
//Hello Michiel,//

on *08.03.22* at *23:07:03* You wrote in Area *WINPOINT*
to *Tim Schattkowsky* about *"WinPoint Version 404 IPV5"*.

 MvdV> Hello Tim,

 MvdV> On Tuesday March 08 2022 20:24, you wrote to me:

 MvdV>>> So, he has IPv6, I have IPv6, he is using WP 404.  but he still
 MvdV>>> comes in with an IPv4 address. Any suggestions?

 TS>> As long as the host also has an IPv4 address, WP will use the IPv4. That
 TS>> is the common practice to aviod trouble with IPv6 infratstructure
 TS>> issues. WP will only use IPv6, if the host only presents an IPv6
 TS>> address.

 MvdV> Ouch! I have been playing around with IPv6 for well over a decade and I
 MvdV> say WP is definitely NOT following common practice. Common practice is
 MvdV> that when the host name resolves to both an IPv4 and an IPv6 address to
 MvdV> try IPv6 first and when that fails to try IPv4.

 MvdV> Maybe we should discuss this in the IPv6 echo. You are welcome to join
 MvdV> there, it is available from your Boss node.

Admittedly, when it comes to IPv6, I still live maybe even more than a decade
ago, when that was a good idea. Had other things to do in between. But I
agree, that the practice is now different, particularly since nowadays the OS
actually takes better care about the Ipv6 connection state. 

Switching this is basically easy. I will do that. However, also implementing a
fallback would take longer and just made it to the end of the list.

Regards,
Tim

--- WinPoint 404.0
 * Origin: Original WinPoint Origin! (2:240/1120.29)
SEEN-BY: 1/120 15/0 18/0 106/201 123/0 129/331 138/146 153/7715 218/700
SEEN-BY: 229/110 317 426 428 664 700 240/1120 250/1 266/512 275/100
SEEN-BY: 275/1000 282/1038 291/111 292/854 301/1 317/3 320/219 335/364
SEEN-BY: 342/11 371/0 396/45 460/58 640/1321 712/848 2452/250 3634/0
SEEN-BY: 3634/12
PATH: 240/1120 3634/12 153/7715 229/426