Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 784  |
|  Michiel van der Vlist to Tim Schattkowsky  |
|  Problem ipv6 vs ipv4  |
|  24 Jun 22 07:58:35  |
 TID: FMail-W32 2.1.3.7-B20170919 RFC-X-No-Archive: Yes TZUTC: 0200 CHRS: CP850 2 MSGID: 2:280/5555 62b55a5f REPLY: 2:240/1120.29 8cefcf84 Hello Tim, On Tuesday June 21 2022 19:24, you wrote to Ulrich Schroeter: TS> Oh. So is this whole IPv4/IPv6 discussion here about the idea that WP TS> should try the other entry from the nodelist? No. The discussion is about fall back to IPv4 in case an attempt to connect via IPv6 fails for whatever reason. I have discussed this with you before. At that time I did not expect this would actually happen but three weeks ago Murphy saw his chance when my provider send me a new modem/router. That modem/router does not support opening ports for incoming IPv6. The host name of my system still presented an AAAA and an A record. So Rinaldo's Winpoint attempt to connect via IPv6 failed. In such a case Winpoint should fall back to IPv4 and try an IPv4 connect. For the time being I have removed the AAAA record from my nodelisted host name, but you can test by using the host name "vlist.eu" instead of the host name in the nodelist. 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 221/0 229/110 SEEN-BY: 229/111 112 113 317 426 428 470 664 700 240/1120 266/512 SEEN-BY: 280/464 5003 5555 282/1038 292/854 8125 301/1 310/31 317/3 SEEN-BY: 320/219 341/234 396/45 460/58 633/280 712/848 770/1 2452/250 PATH: 280/5555 464 712/848 229/426 |
[ << oldest | < older | list | newer > | newest >> ]