home bbs files messages ]

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,143 of 4,612   
   Michiel van der Vlist to Tony Langdon   
   finaly for me   
   19 Mar 18 13:01:14   
   
   Hello Tony,   
      
   On Monday March 19 2018 10:53, you wrote to me:   
      
    MvV>> On average of course, but my impressiosn is that there are a lot of   
    MvV>> nodes that just run on inertia rather than active sysop involvement.   
    MvV>> You will find less of those among the members of the IPv6 club.   
      
    TL> Yes, you need to take active steps in a lot of cases,   
      
   For starters: 30% of the nodes in my list of IPv6 capable nodes still connect   
   via a tunnel. Setting uo a tunnel certainly requires taking active steps.   
      
    TL> IPv6 may not be automatically enabled in some Fido software (that   
    TL> supports it). Network wise, it depends on your ISP.  Mine enables IPv6   
    TL> by default and all of the routers they provide support IPv6 out of the   
    TL> box, so at the network level it should "just work".   
      
   Your ISp is a pioneer. Many ISPs around the world are still dragging their   
   feet. So " just work" is still the exception rather than te rule.   
      
    TL> Wasn't the case for me, but that's because I added IPv6 before it went   
    TL> into production.  It was still a trial service (back in early 2011),   
    TL> and I had to turn it on to enable the trial, once I had a router that   
    TL> was IPv6 capable.  That trial service did eventually become the   
    TL> production service I'm on today.   
      
   I have native Dual Stack now for over a year, but my ISP is also one of the   
   slow ones. Plus that now their policy is to go DS -Light. New customers get   
   DS-Light. On request they can be converted ti IPv4 only.  That is another   
   spoke in the whell of "just work".   
      
    MvV>> Same here. Plus that when adding new links and having to make a   
    MvV>> choice, I prefer to link to the IPv6 capable node over linking   
    MvV>> to the IPv4 only node.   
      
    TL> Me too, I think around 50% of my upstream links have IPv6 here.   
      
   Same here, around 50%. In future, I may even drop some IPv4 only links to up   
   the percentage. ;-)   
      
      
   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