TID: FMail-W32 2.1.3.7-B20170919   
   TZUTC: 0200   
   CHRS: CP850 2   
   MSGID: 2:280/5555 5cd3e52e   
   REPLY: 1:282/1031.0 84c27ec7   
   Hello Jeff,   
      
   On Wednesday May 08 2019 08:07, you wrote to me:   
      
   Your script seems to be working. I can connect now:   
      
     09:38 [1760] clientmgr started   
   + 09:38 [2984] call to 1:282/1031@fidonet   
     09:38 [2984] trying f1031.n282.z1.binkp.net [2602:41:670c:a600   
   d597:9bc0:8b9f:2c92]...   
     09:38 [2984] connected   
   + 09:38 [2984] outgoing session with f1031.n282.z1.binkp.net:24554   
                  [2602:41:670c:a600:d597:9bc0:8b9f:2c92]   
   - 09:38 [2984] SYS The Ouija Board   
   - 09:38 [2984] ZYZ Jeff Smith   
   - 09:38 [2984] LOC Anoka, MN - bbs.ouijabrd.net   
   - 09:38 [2984] VER BBBS/Li6 v4.10 Toy-4 binkp/1.0   
   - 09:38 [2984] NDL CM,IBM,IFT,INA   
   + 09:38 [2984] addr: 1:282/1031@fidonet   
      
    >> Odd. An ISP should know what address (blocks) they issue...   
      
    JS> Yes. The support staff seemed to know what a v6 IP was but didn't   
    JS> appear to know much about them. I would get the "Sorry, I don't have   
    JS> that information available". And they would then transfer me to   
    JS> someone who would end up giving me the same response.   
      
   That does not give much confidence that they have people with the required   
   knowledge... :(   
      
    JS> Here in Linux for a manual/static v4 IP setup one has to provide the   
    JS> v4 IP, the subnet mask, and the gateway address. Similarly for v6   
    JS> manual/static IP setup on has to specify the v6 IP, the prefix, and   
    JS> the v6 gateway address. All three have to be specified to be able to   
    JS> save the v4 or v6 IP network settings.   
      
   But why the need for manual configuration? The IPv6 protocol was designed to   
   NOT need such things. Not for dynamic and not for static addresses. The CPE   
   (the router at your home) negotiates an IPv6 prefix with the ISP via prefix   
   delegation. The router advertises the prefix on the LAN and interfaces on the   
   LAN are assigned addresses by SLAAC or DHCP6 using that prefix. No need fo   
   user intervention.   
      
    JS> Here, the router is setup to accept and support a static IP block. And   
    JS> will accept traffic for any of the static IP's in that block. Each PC   
    JS> is assigned a static IP and accepts traffic for that particular static   
    JS> IP. The router doesn't assign an IP to the PC unless DHCP is in use.   
    JS> Here DHCP is in use but only for assigning local non-routeable IP's.   
      
   It seems to me that your ISP runs some stripped version of IPv6... :(   
      
    >> It is only when running servers that I have to intervene. I have to   
    >> punch a hole in the firewall for the ports concerned and I have to   
    >> update the DNS..   
      
    JS> Yes similarly here I have to make the necessary ports available.   
      
   But only for running servers. Configuring clients should be automatic without   
   the need for user intervention.   
      
    >> Can you change ISPs in you area?   
      
    JS> Sadly, that isn't an option as Centurylink (Qwest) is the only fiber   
    JS> based ISP in the area and the only other options are cable or   
    JS> satellite. Neither of which (Last time I checked) provided static   
    JS> IP's.   
      
   So you are stuck wih them. :(   
      
      
   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 393/68 423/120 460/58   
   SEEN-BY: 633/280 640/1384 712/848 770/1 2452/250 3828/7 5019/40 5020/545   
   SEEN-BY: 5020/1042 12000 5053/58   
   PATH: 280/5555 464 229/426