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 1,860 of 4,612    |
|    Michiel van der Vlist to Konstantin Kuzov    |
|    Another one!    |
|    09 Jan 18 14:45:28    |
      Hello Konstantin,              On Tuesday January 09 2018 11:48, you wrote to me:               KK>>> That's fido IPv6 relay for binkp and ifcico I made just for        KK>>> lulz.        MvdV>> So this is an IPV6 to IPv4 gateway.               KK> Actually, it isn't strictly IPv6 to IPv4. IPv6 to IPv6 also works.              Yes, that works too. I could reach IPv6 only node 280/5006 via       2a04:52c0:101:201:f1d0:2:280:5006               KK> And if destination IPv4 addresses are unresponsive IPv6 addresses also        KK> will be tried.              That does not work. If I diasble listen 0.0.0.0 on my main machine I get       "connection refused" when trying to connect to it via your gateway.               KK> So it is potentially can be used to reach IPv6-only        KK> nodes if direct routing isn't working for some reason.              Hmmm...               MvdV>> IPv6 only nodes can use this to connect to IPv4 only nodes.        MvdV>> Wow!.               KK> Or IPv4 only nodes could use such services to advertise IPv6        KK> reachability when don't want to mess with IPv6 tunnels              "Messing" with a tunnel was an interesting and lerningful experience. And a       tunnel is much more flexible, it not only offers BINKP and IFCICO. It can be       used for ALL services.               KK> or their retro-OS doesn't support IPv6 at all.              Dump it! ;-)               KK> Or just want a shiny f1d0-style address but can't have one...              Minor cosmetic issue...               KK> There are could be numerious hypotetical reasons for such services to        KK> exist.              Perhaps...              But I think that with the coming of DS_Lite the reverse would be more useful.       But harder to implement...              But then I think I'd prefer to use the services of an agent independant of       Fidonet. Such as http://www.feste-ip.net/ They are still a SPOF, but most       likely have no interest in acting as a SPOM.               MvdV>> I do not know what problem this is a solution for, AFAIK there        MvdV>> are no truly IPv6 only connections yet. Every end user on the        MvdV>> internet still has outgoing IPv4 capability and probably will        MvdV>> have that for a very long time to come. But this certainly is        MvdV>> an interesting experiment. Tell us more... Write a Fidonews        MvdV>> article...               KK> As I have already said that experiment was just for fun.              OK. ;-)               KK> I've tested how recent linux kernels handle thousands of address        KK> aliases on interfaces in memory constrained environment. I hadn't        KK> intended and still don't intent to provide such service for anyone to        KK> use in real life. As it's prone to abuse and centralization.              Indeed. Experience unfortunately shows that in Fidonet centralisation may lead       to manipulation. :-(               KK> But as my address was noticed and mistaken as potential new IPv6 fido        KK> member I clarified that it's not. ^_^              Good that this is cleared up.               KK>>> There are two IPv6 prefixes:        KK>>> - "f1d0 style" - 2a04:52c0:101:201:f1d0::/80        KK>>> - "hex style" - 2a04:52c0:101:201:fed0::/80               MvdV>> I may test that hex option later.              The hex option works.                     Cheers, Michiel              --- GoldED+/W32-MSVC 1.1.5-b20170303        * Origin: he.net certified sage (2:280/5555)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca