• IPv6's

    From Jeff Smith@1:282/1031 to All on Tuesday, May 07, 2019 12:25:32
    Hello There,

    First, let me say that I am far from overly knowledgeable regarding IPv6 operation and functionality.

    But after talking, being on hold to several levels of my ISP's support staff over the last two hours. I feel pretty dang smart. :-)

    I had to explain my IP situation several different ways before I could get them
    to comprehend what I actually needed. My situation is really quite simple to me. I have a block of static v4 IP's I am told by my ISP that each static v4 IP
    has a derived v6 IP assigned to it. 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. Linux needs to know those settings before one can save the network settings for that that Linux PC. 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.

    Jeff

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)
  • From Michiel van der Vlist@2:280/5555 to Jeff Smith on Wednesday, May 08, 2019 10:35:21
    Hello Jeff,

    On Tuesday May 07 2019 12:25, you wrote to All:

    First, let me say that I am far from overly knowledgeable regarding
    IPv6 operation and functionality.

    But after talking, being on hold to several levels of my ISP's support staff over the last two hours. I feel pretty dang smart. :-)

    ;-)

    Unfortunately it stopped working again:

    + 10:14 [2640] call to 1:282/1031@fidonet
    10:14 [2640] trying f1031.n282.z1.binkp.net [2602:41:670c:a600:d1d2:c23d:4b1c:940c]...
    ? 10:15 [2640] connection to 1:282/1031@fidonet failed: {W32
    API error 10065} A socket operation was attempted to an unreachable host
    10:15 [2640] trying f1031.n282.z1.binkp.net [65.103.12.161]:24554...
    + 10:15 [2640] bind -- getaddrinfo: Der angegebene Host ist unbekannt. (11001)
    10:15 [2640] connected
    + 10:15 [2640] outgoing session with f1031.n282.z1.binkp.net:24554 [65.103.12.161]

    I had to explain my IP situation several different ways before I could
    get them to comprehend what I actually needed. My situation is really quite simple to me. I have a block of static v4 IP's I am told by my
    ISP that each static v4 IP has a derived v6 IP assigned to it.

    Hmmm...

    There is a way to associate an IPv6 address with an IPv4 address, there is even
    a notation for it:

    2001:1c02:1100:d200::192.168.178.11

    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...

    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 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.

    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..

    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. :(

    Can you change ISPs in you area?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Benny Pedersen@2:230/0 to Michiel van der Vlist on Wednesday, May 08, 2019 10:32:58
    Hello Michiel!

    08 May 2019 10:35, Michiel van der Vlist wrote to Jeff Smith:

    MvdV> 2001:1c02:1100:d200::192.168.178.11
    MvdV> But I have never seen this actually used by an ISP to issue IPv6.

    isps on steriods

    when ipv6 come, it will kill natting and or expensive paid for more ips, cheaper internet to all, lower ram usage by not needing dual ip stacks

    dream on, back to the future


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.1.2 (Linux/4.19.27-gentoo-r1 (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Jeff Smith@1:282/1031 to Michiel Van Der Vlist on Wednesday, May 08, 2019 08:07:32
    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)
  • From Michiel van der Vlist@2:280/5555 to Jeff Smith on Thursday, May 09, 2019 10:30:37
    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...

    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.

    That does not give much confidence that they have people with the required knowledge... :(

    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.

    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.

    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 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..

    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?

    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.

    So you are stuck wih them. :(


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)