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 3,398 of 4,612    |
|    Tony Langdon to Victor Sudakov    |
|    Re: Down Temporarily    |
|    31 Jan 21 19:01:00    |
      TZUTC: 1100       MSGID: 1671.fido-ipv6@3:633/410 247bb59b       REPLY: 2:5005/49 601639c2       PID: Synchronet 3.17c-Linux Nov 3 2019 GCC 4.6.3       TID: SBBSecho 3.10-Linux r3.146 Nov 3 2019 GCC 4.6.3       CHRS: ASCII 1       -=> On 01-31-21 11:53, Victor Sudakov wrote to Jay Harris <=-               VS> I have been always of the opinion that port forwarding is never needed        VS> in IPv6 because no NAT is ever involved (and port forwarding is part of        VS> the destination NAT technology). If you had IPv6 port forwarding (in        VS> the IPv4 way) on some device, please surprise me!              Some consumer routers mislabel IPb6 firewall opening as "port forwarding", mine       included. Mine came with all inblund IPv6 traffic blocked by default (good!),       but to open a port to a specific host, I have to go into "IPv6 port forwarding"       (sic) and specify the port(s) that I want to open and the interface host ID       (last 64 bits of the IPv6 address) to allow traffic for. Or I can specify that       host as an "exposed host", which of course, disables the firewall for that       specific IPv6 address.               VS> It is also difficult to believe that a fancy router does not have a        VS> built-in IPv6 firewall (if a firewall is meant by "port opening").              One would hope it does, and that there's a mechanism to open ports to specific       hosts in the firewal config.               VS> My home MikroTik hAP ac3 does not support NAT or port forwarding in        VS> IPv6 (which is expected) but has a nice IPv6 stateful firewall with        VS> connection tracking (in fact it's iptables inside). I have eventually        VS> moved all my IPv6 tunneling to MikroTik and I'm very happy about it's        VS> performance.              My router does speak of IPv6 port forwarding, but it's actually controlling the       firewall's packet filter.                      ... Is fire supposed to shoot out of it like that!?       === MultiMail/Win v0.52       --- SBBSecho 3.10-Linux        * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)       SEEN-BY: 1/123 90/1 105/81 120/340 123/131 226/30 227/702 229/424       SEEN-BY: 229/426 550 664 1016 240/5832 249/206 317 400 317/3 322/757       SEEN-BY: 342/200 633/0 267 280 281 410 412 416 509 640/1384 712/848       PATH: 633/410 280 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca