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 3,790 of 4,612   
   Michiel van der Vlist to Anna Christina Nass   
   List of IPv6 nodes   
   06 Jan 22 13:10:11   
   
   TID: FMail-W32 2.1.3.7-B20170919   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: CP850 2   
   MSGID: 2:280/5555 61d6de52   
   REPLY: 2:240/5824.1@fidonet f82e9ab5   
   Hello Anna,   
      
   On Thursday January 06 2022 08:55, you wrote to me:   
      
    MvdV>> I never understood why providers still issue dynamic adresses to   
    MvdV>> their customers. It made sense in the time of dial up. But now   
    MvdV>> with "always on" connections...   
      
    AN> I think, today it is a way to sell their 'business' rates which   
    AN> include static IPv4 and IPv6 prefix...   
      
   Here that "Business Pro" package is not available without a commercial   
   registration.   
      
    MvdV>> Anyway, I too have a dynamic IPv4 address and a dynamic IPv6   
    MvdV>> pefix. But in practice it is semi static. It does not change   
    MvdV>> often enough to invest time and energy in automatic updates.   
      
    AN> My first boss once told me: If something is to be done more than one   
    AN> time, it's worth writing a script to automate it :)   
      
   I see the point but I disagree with that boss of yours. If it happens twice it   
   is still not worth to invest time and energy in automating it. Most of the   
   time at least. Problem is of course that one generally does not know in   
   advance how often it is going to happen. I intended to automate the DNS   
   update, I simply never got around doing it. If it were to happen once a week,   
   I would have done it by now, but as it is, it simply does not have priority.   
      
    AN> But besides, you have to be noticed somehow that the IP/prefix has   
    AN> been changed - or how do you know when to manually update your DNS?   
      
   If my IPv6 pefix changes I notice soon enough. There is always someone in the   
   Fidonet IPv6 club that warns me within a day. ;-)   
      
      
   Cheers, Michiel   
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: he.net certified sage (2:280/5555)   
   SEEN-BY: 1/123 15/0 19/10 30/0 80/1 90/1 105/81 106/201 120/340 123/131   
   SEEN-BY: 153/7715 154/10 203/0 221/0 1 6 226/30 229/424 426 428 550   
   SEEN-BY: 229/664 700 240/1120 5832 249/206 317 400 250/1 266/512 280/464   
   SEEN-BY: 280/5003 5006 5555 282/464 1038 301/0 1 101 113 812 310/31   
   SEEN-BY: 317/3 320/219 322/757 342/200 396/45 460/58 633/280 640/1384   
   SEEN-BY: 712/848 920/1 2452/250 5019/40 5020/545 1042 12000 5053/58   
   SEEN-BY: 5058/104   
   PATH: 280/5555 301/1 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca