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,872 of 4,612   
   Jeff Smith to Michiel Van Der Vlist   
   IPv6's   
   08 May 19 08:07:32   
   
   MSGID: 1:282/1031.0 84c27ec7   
   REPLY: 2:280/5555 5cd2982c   
   TZUTC: -0600   
   CHARSET: PC-8   
   Hello Michiel.   
      
   > On Tuesday May 07 2019 12:25, you wrote to All:   
      
   > But I have never seen this actually used by an ISP to issue IPv6.   
      
   >> I asked them what the v6 Prefix and the v6 Gateway address(s) were.   
   >> They had little if any knowledge what my v6 IP's were let alone what   
   >> the prefix or gateway would be.   
      
   > Odd. An ISP should know what address (blocks) they issue...   
      
   Yes. The support staff seemed to know what a v6 IP was but didn't appear to   
   know   
   much about them. I would get the "Sorry, I don't have that information   
   available". And they would then transfer me to someone who would end up giving   
   me the same response.   
      
   >> Linux needs to know those settings before one can save the network   
   >> settings for that that Linux PC.   
      
   >I am not familiair with Linux, but I would be surprised if it differs, in that   
   > contrary to Windows, it requires user intervention to ceate a working IPv6   
   > setup.   
      
   Here in Linux for a manual/static v4 IP setup one has to provide the v4 IP,   
   the subnet mask, and the gateway address. Similarly for v6 manual/static IP   
   setup on has to specify the v6 IP, the prefix, and the v6 gateway address. All   
   three have to be specified to be able to save the v4 or v6 IP network settings.   
      
   > Here I do not have to do anything to assign IPv6 addresses to my PC's. The   
   > router is assigned a /56 from the ISP. The router assigns a /64 to the local   
   >LAN en from that /64 IPv6 addresses are assigned to devices on the LAN. Either   
   > bij SLAAC or DHCP6.   
      
   Here, the router is setup to accept and support a static IP block. And will   
   accept traffic for any of the static IP's in that block. Each PC is assigned a   
   static IP and accepts traffic for that particular static IP. The router   
   doesn't assign an IP to the PC unless DHCP is in use. Here DHCP is in use but   
   only for assigning local non-routeable IP's.   .   
   > 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..   
      
   Yes similarly here I have to make the necessary ports available.   
      
   >> I have written a bash script that goes out and gets my v6 IP and IF it   
   >> has changed it then updates the settings at my DNS provider for that   
   >> domain. Which shouldn't be needed IF the v6 IP was actually static   
   >> like they say that it is.   
      
   > So obviously you do not have static IPv6 addresses. :(   
      
   Yes... Sadly that would be my conclusion also. They state that "A static v6 IP   
   isn't necessary since each v6 IP is derived from a staticv4 IP". The question   
   I then asked was why does the IP change? Again... I got the "Sorry, I don't   
   have that information".   
      
   > Can you change ISPs in you area?   
      
   Sadly, that isn't an option as Centurylink (Qwest) is the only fiber based ISP   
   in the area and the only other options are cable or satellite. Neither of   
   which (Last time I checked) provided static IP's.   
      
   Jeff   
      
   --- BBBS/Li6 v4.10 Toy-4   
    * Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)   
   SEEN-BY: 1/19 123 14/5 15/0 2 16/0 19/36 34/999 90/1 116/18 120/331   
   SEEN-BY: 123/130 131 128/2 153/7715 154/10 203/0 218/700 221/0 1 6   
   SEEN-BY: 221/360 226/17 229/354 426 1014 230/0 150 152 240/1120 5832   
   SEEN-BY: 249/206 317 400 250/1 261/38 100 267/155 275/100 280/464   
   SEEN-BY: 280/5003 5006 5555 282/1031 1056 291/1 111 292/854 298/25   
   SEEN-BY: 298/26 310/31 317/3 320/119 219 322/0 757 340/400 342/13   
   SEEN-BY: 342/200 393/68 423/120 633/280 640/1384 712/848 770/1 801/189   
   SEEN-BY: 2320/105 2452/250 3634/12 3828/7 5020/545   
   PATH: 282/1031 261/38 320/219 221/1 280/464 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca