Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 656  |
|  Michiel van der Vlist to Tim Schattkowsky  |
|  WinPoint Version 404 IPV5  |
|  09 Mar 22 00:07:03  |
 TID: FMail-W32 2.1.3.7-B20170919 RFC-X-No-Archive: Yes TZUTC: 0100 CHRS: CP850 2 MSGID: 2:280/5555 6227e2bb REPLY: 2:240/1120.29 451d2f03 Hello Tim, 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. TS> That 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. Ouch! I have been playing around with IPv6 for well over a decade and I say WP is definitely NOT following common practice. Common practice is that when the host name resolves to both an IPv4 and an IPv6 address to try IPv6 first and when that fails to try IPv4. Maybe we should discuss this in the IPv6 echo. You are welcome to join there, it is available from your Boss node. Cheers, Michiel --- GoldED+/W32-MSVC 1.1.5-b20170303 * Origin: he.net certified sage (2:280/5555) SEEN-BY: 15/0 106/201 124/5016 129/331 153/757 7715 203/0 218/700 SEEN-BY: 221/0 229/110 317 426 428 664 700 266/512 280/464 5003 5555 SEEN-BY: 282/1038 292/854 8125 301/1 310/31 317/3 320/219 341/234 SEEN-BY: 396/45 460/58 712/848 770/1 2452/250 PATH: 280/5555 464 712/848 229/426 |
[ << oldest | < older | list | newer > | newest >> ]