TZUTC: -0700   
   MSGID: 2.ipv6@1:103/705 288fc8b9   
   REPLY: 2:280/5555 6429e8be   
   PID: Synchronet 3.20a-Win32 master/28e825909 Apr  1 2023 MSC 1929   
   TID: SBBSecho 3.20-Linux master/f5d4c9bdb Mar 31 2023 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.104   
     Re: Connection Tests   
     By: Michiel van der Vlist to Rob Swindell on Sun Apr 02 2023 10:36 pm   
      
    >   
    > *** Answering a msg posted in area FIDOTEST (FIDOTEST).   
    >   
    > Hello Rob,   
    >   
    > On Sunday April 02 2023 12:43, you wrote to me:   
    >   
    >  >> I see you took the easy way out. You removed the AAAA record from   
    >  >> the DNS.   
    >   
    >  RS> For now. No point advertising an incorrect address.   
    >   
    > Indeed. For the BBS it may even annoy the users. With the IPv6 address in   
    > place a user that is running an IPv6 capable terminal program may have to   
    > wait a minute or so for his software to realize that IPv6 is not working and   
    > fall back to IPv4.   
    >   
    >  >> Perhaps you should come to the IPv6 echo. That is where the   
    >  >> expertise is...   
    >   
    >  RS> Will do.   
    >   
    > So... here I am...   
      
   So my ISP (Spectrum, aka Comcast Business) enabled IPv6 for me recently (after   
   many years of service and unanswered inquiries from me about IPv6 support)   
   without any notice or explanation. I have 5 static IPv4 addresses (a so-called   
   "5 pack"), but I have no idea if I also have static IPv6 addresses or what   
   they are.   
      
   For my public network interface on my Windows box (vert.synchro.net), ipconfig   
   reports:   
      
   Ethernet adapter Internet:   
      
      Connection-specific DNS Suffix  . :   
      Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network   
   Connection #2   
      Physical Address. . . . . . . . . : 00-25-90-85-ED-7D   
      DHCP Enabled. . . . . . . . . . . : No   
      Autoconfiguration Enabled . . . . : Yes   
      IPv6 Address. . . . . . . . . . . : 2600:6c88:8c40:5b::f5a(Preferred)   
      Lease Obtained. . . . . . . . . . : Sunday, April 02, 2023 10:35:32 PM   
      Lease Expires . . . . . . . . . . : Sunday, April 09, 2023 10:35:23 PM   
      IPv6 Address. . . . . . . . . . . : 2600:6c88:8c40:5b:7d15:cb   
   2:16c5:350c(Preferred)   
      Temporary IPv6 Address. . . . . . : 2600:6c88:8c40:5b:c89:48b   
   :f442:1e7b(Deprecated)   
      Temporary IPv6 Address. . . . . . : 2600:6c88:8c40:5b:4964:18   
   3:2b0d:df6d(Preferred)   
      Link-local IPv6 Address . . . . . : fe80::9ec:7a2:d500:1bf8%19(Preferred)   
      IPv4 Address. . . . . . . . . . . : 71.95.196.34(Preferred)   
      Subnet Mask . . . . . . . . . . . : 255.255.255.248   
      Default Gateway . . . . . . . . . : fe80::eaad:a6ff:fe58:de1a%19   
                                          71.95.196.33   
      DHCPv6 IAID . . . . . . . . . . . : 67118480   
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-F4-0D-4C-0   
   -25-90-85-ED-7D   
      DNS Servers . . . . . . . . . . . : 2607:f428:ffff:ffff::1   
                                          2607:f428:ffff:ffff::2   
                                          192.168.1.2   
                                          1.1.1.1   
                                          2607:f428:ffff:ffff::1   
                                          2607:f428:ffff:ffff::2   
      NetBIOS over Tcpip. . . . . . . . : Disabled   
      
   When I connect out to an Internet site (e.g. whatismyipaddress.com), it says   
   I'm connecting from 2600:6c88:8c40:5b:915d:3a98:8ac1:7886, but I'm pretty sure   
   that address changes.   
      
   For my public network interface on my Debian Linux box (cvs.synchro.net), 'ip   
   a' reports:   
      
   2: enp1s0:  mtu 1500 qdisc mq state UP group   
   de                                                   fault qlen 1000   
       link/ether 00:10:18:2a:1a:b6 brd ff:ff:ff:ff:ff:ff   
       inet 71.95.196.35/29 brd 71.95.196.39 scope global enp1s0   
          valid_lft forever preferred_lft forever   
       inet 71.95.196.36/29 brd 71.95.196.39 scope global secondary enp1s0   
          valid_lft forever preferred_lft forever   
       inet 71.95.196.37/29 brd 71.95.196.39 scope global secondary enp1s0   
          valid_lft forever preferred_lft forever   
       inet6 2600:6c88:8c40:5b:210:18ff:fe2a:1ab6/64 scope global dynamic   
   mngtmpadd                                                   r noprefixroute   
          valid_lft 604780sec preferred_lft 604780sec   
       inet6 fe80::210:18ff:fe2a:1ab6/64 scope link   
          valid_lft forever preferred_lft forever   
      
   My ISP provided router appears to be a Sagemcom, but I don't know much more   
   about it (I use my own wireless access points and routers for DH   
   P/NAT/Firewall for the other devices on my internal/private networks). The ISP   
   router (the Sagemcom) web UI reports that the vert.synchro.net system has IPv6   
   address 2600:6c88:8c40:5b::f5a, but when I attempt to connect to that IPv6   
   address or the ::7886 address (or even just ping6 them) from a remote host, I   
   don't have any success.   
      
   Still a bit mysterious to me with so many addresses and so little information   
   from the ISP. Any tips are welcome,   
   --    
                                               digital man (rob)   
      
   Sling Blade quote #8:   
   Karl Childers: I don't reckon I got no reason to kill nobody.   
   Norco, CA WX: 51.0øF, 92.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.20-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 1/123 10/0 1 15/0 90/1 103/705 104/117 105/81 106/201 123/131   
   SEEN-BY: 153/7715 214/22 218/0 1 215 700 860 226/30 227/114 229/110   
   SEEN-BY: 229/111 112 113 206 307 317 400 424 426 428 452 470 550 664   
   SEEN-BY: 229/700 266/512 282/1038 317/3 320/219 322/757 342/200 396/45   
   SEEN-BY: 633/280   
   PATH: 103/705 218/700 229/426