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,116 of 4,612    |
|    Rob Swindell to Michiel van der Vlist    |
|    Connection Tests    |
|    04 Apr 23 13:23:16    |
      TZUTC: -0700       MSGID: 18.ipv6@1:103/705 2891bd46       REPLY: 2:280/5555 642c194d       PID: Synchronet 3.20a-Linux master/0f4325eec Apr 3 2023 GCC 12.2.0       TID: SBBSecho 3.20-Linux master/fcf4a0012 Apr 4 2023 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       NOTE: FSEditor.js v1.104        Re: Connection Tests        By: Michiel van der Vlist to Rob Swindell on Tue Apr 04 2023 02:34 pm               > Hello Rob,        >        > On Monday April 03 2023 10:35, you wrote to deon:        >        > RS> I've never used the ISP's router's port        > RS> blocking/forwarding/NAT/gateway features before (for IPv4), so now I'm        > RS> looking what it supports. It does have DHCPv6 and DHCP-PD was        > RS> disabled, so I've enabled that and expecting for it to hand out        > RS> addresses in the range:        >        > RS> 2600:6c88:8c40:5b::1 to ::1000 (according to its default        > RS> configuration)        >        > RS> I haven't seen that happen yet.        >        > But it has assigned 2600:6c88:8c40:5b::f5a to your Fidonet machine.              Using that as vert's public IPv6 and adding it to the ISP router's DMZ (and       IPV6 DMZ, they're 2 different settings) did the trick. |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca