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 2,979 of 4,612    |
|    Michiel van der Vlist to Jeff Smith    |
|    IP6 Tunnel?    |
|    02 Aug 19 13:05:35    |
      TID: FMail-W32 2.1.3.7-B20170919       RFC-X-No-Archive: Yes       TZUTC: 0200       CHRS: CP850 2       MSGID: 2:280/5555 5d441d1d       REPLY: 1:282/1031.0 346db319       Hello Jeff,              On Thursday August 01 2019 09:43, you wrote to me:               >> Are you aware that - if they are on the same LAN - you do not need a        >> sepearate tunnel for each node, but that you can have a routed subnet        >> (/64 or /48) from he.net and use just one tunnel for all the nodes om        >> your LAN?               JS> I had the understanding that the tunnel was related to a static v4        JS> endpoint IP. Here each PC (FTN Node) has it's own static v4 IP. Are        JS> you saying that a single tunnel can support multiple static v4 IP        JS> endpoints?              The tunnel does not "support" a static IPv4 endpoint. It is more the other way       around. A tunnel needs a public IPv4 address for its end point. The same       public IPv4 address can be used for other purposes, such as a Fidonet Binkp       server. But it need not be. The fact that the tunnel is used to supply an IPv6       address to the same binkd server is irrelevant. The binkp server can be on a       different IPv4 address than the tunnel servicing the IPOv6 part.              Yes, for a second tunnel, you need a different public IPv4 address for the end       point.              My point is: you probably do not need a second tunnel. A tunnel is a channel       to the rest of the world that can handle many IPv6 addresses. Just like an       IPv4 router can make you connect many device to the IPv4 internet via a single       channel, so can a tunnel for IPv6.              You can assign different IPv6 addresses to 1:282/1031 and 1:14/6 over one and       the same tunnel.              How this is done and if it is "better" in your situation is another matter.                     Cheers, Michiel              --- GoldED+/W32-MSVC 1.1.5-b20170303        * Origin: he.net certified sage (2:280/5555)       SEEN-BY: 1/123 15/2 19/10 154/10 203/0 221/0 6 226/17 229/354 426       SEEN-BY: 229/1014 240/5832 249/206 317 400 280/464 5003 5006 5555       SEEN-BY: 292/854 310/31 317/3 322/757 342/200 423/120 460/58 633/280       SEEN-BY: 640/1384 712/848 770/1 2452/250 3828/7 5019/40 5020/545 1042       SEEN-BY: 5020/12000 5053/58       PATH: 280/5555 464 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca