Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    IPV6    |    The convoluted hot-mess that is IPV6    |    4,612 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 4,487 of 4,612    |
|    Michiel van der Vlist to Dmitry Protasoff    |
|    New ones    |
|    14 Oct 25 10:20:56    |
      TID: FMail-W32 2.3.0.1-B20240319       RFC-X-No-Archive: Yes       TZUTC: 0200       CHRS: CP850 2       MSGID: 2:280/5555 68ee09b2       REPLY: 2:5001/100.1 68ed2171       Hello Dmitry,              On Monday October 13 2025 18:52, you wrote to me:               MV>> 56 IPv6 non-working nodes found.               MV>> That's more than I expected. There is work to do!               DP> Please note (this is also written on the website):               DP> for working nodes:        DP> This report shows nodes that have IPv6 addresses resolved and have        DP> been successfully tested with at least one protocol over the last 30        DP> days.               DP> for non working nodes:        DP> This report shows nodes that have IPv6 addresses (either from nodelist        DP> or resolved from hostnames) but no IPv6 services are currently working        DP> over the last 30 days.               DP> So a node will be moved from working to non-working state only after        DP> 30 days of loosing ipv6 access.              I take it that applies to existing nodes that once had working IPv6       connectivity and become nonworking at some point. But how about /new/ nodes       that advertise IPv6 connectivity but never had it working?              I also note that a significant fraction of the 56 nodes in the list of non       working IPv6 nodes ha no connectivity at all. No IPv6 /and/ no IPv4. It is not       what I expected but I can live with it.              I have send netmail to all the nodes that have IPv4 connectivity but no       working IPv6. We shall see where that brings us.               DP> I'll add a simple API to get these reports and updates with curl, but        DP> I need to refactor the code first: it was written before I even knew        DP> what this website would become and it's a bit of a mess :)              I stay tuned...                     Cheers, Michiel              --- GoldED+/W32-MSVC 1.1.5-b20170303        * Origin: he.net certified sage (2:280/5555)       SEEN-BY: 10/0 1 19/10 103/705 104/117 105/81 106/201 124/5016 128/187       SEEN-BY: 129/14 153/757 7715 154/10 30 110 203/0 214/22 218/0 1 215       SEEN-BY: 218/610 620 700 860 221/0 226/30 227/114 229/110 206 317       SEEN-BY: 229/400 426 428 470 616 664 700 705 240/1120 5832 250/1 263/1       SEEN-BY: 266/512 280/464 5003 5006 5555 291/111 292/854 8125 301/1       SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120       SEEN-BY: 460/58 467/888 633/280 712/848 770/1 902/26 5019/40 5020/400       SEEN-BY: 5020/545 1042 5053/58 5075/35       PATH: 280/5555 464 103/705 218/700 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca