> > *** 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:
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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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 DHCP/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)
