Didn't find what you were looking for?


We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.

IPv6 ??

fmouse
fmouse Posts: 32 Contributor
edited August 28 in Connectivity

I have Spectrum residential service and several years ago Spectrum started handing out /128 IPv6 addresses, and this would show up automatically (DHCP) in my interface table for my WAN NIC. I have service on a commercial server, unaffiliated with Spectrum, which has given me a /56 IPv6 address assignment for my use and I successfully routed a piece of this group, via my Spectrum connection and a VPN, for use for v6 addresses on our LAN, using OpenVPN. This worked perfectly for a number of years! About a year ago I noted that the VPN routing for v6 addresses stopped working, and apparently Spectrum is no longer gives me a v6 address. NOTHING CHANGED ON OUR END.

Has something changed with Spectrum's policy? I don't need a static v4 or v6 address, just a way of connecting to the IPv6 universe so that I can operate my LAN, so a dynamically assigned (and properly routed) v6 address would work fine.

I read somewhere that Spectrum is now assigning EITHER a v4 OR a v6 address on connection in response to a DHCP client request. Is this the case?

Answers

  • HT_Greenfield
    HT_Greenfield Posts: 926 Contributor

    It's all Greek to me but all i can figure is that you should be getting a /64 if not /60 prefix although i wouldn't be surprised if /60 is only for biz-grade and/or maybe top-tier residential subscribers.

    🔗https://www.spectrum.net/support/internet/ipv6

    🔗https://www.spectrum.net/support/internet/ipv6-faq

    If it's not happening, you could always try to re-up it on the router with e.g. auto-detect selected in lieu of any more specific connection type.

  • RAIST515O
    RAIST515O Posts: 213 Contributor

    Want to say it was /56, and passthrough only back when I tinkered with it years ago.

    Wound up turning it off on my router though because of issues with some games. Since I play nearly 99% on console nowadays, just never bothered with it since.

  • fmouse
    fmouse Posts: 32 Contributor
    edited June 11

    I'm not interested in anything bigger than a /128 IPv6 connection from Spectrum since I have a VPN to my server which provides me with a /56, and I can assign v6 addreses to our LAN hosts from this group.. But without even a single IPv6 address (which I used to have) I can't run a v6 VPN from my LAN. I'm interested in Spectrum's policy with regard to assignment of V6 addresses. I don't need a fixed address, just one that works. I repeat, this Used to work, and did so for a number of years, but stopped working relatively recently (last year or so). Nothing has in my hardware or software router configuration which would have caused this.

    I've heard that Spectrum's policy for residential service has changed, and one now gets either a v4 or a v6 address via DHCP (or DHCP6). Can anyone who understands the technology confirm this?

  • RAIST515O
    RAIST515O Posts: 213 Contributor

    Tinkered with it at the house for another thread recently. All I did was go into the Asus config and turn it on as Native... left everything at defaults (auto configs).

    Was able to go back in and do both /64 and /56 requests and got both, but did not try any others.

    While the linux box, phones, and streaming devices got along with the v6 fine... the Windoze laptop was still being fussy about it. Since I don't have a need for v6, and all the games I play are still using v4 anyway... just turned it back off again.

  • fmouse
    fmouse Posts: 32 Contributor

    The problem is mooted/solved. I'm running a TAP (Ethernet) level VPN connection from our LAN's gateway Linux box to my company's server, and the hosting company (Akamai née Linode) has granted me a /56 IPv6 address group. I was routing this address group to my LAN, via the VPN (OpenVPN). For some reason this connection worked up until a couple of years ago, and then quit. I was assuming, without examining my original work, that the VPN was relying on the assignment of a v6 address from Spectrum, which turned out not to be the case.

    It appears that Linux updated the IPv6 stack at some point to require that host to host routing use link local addresses, whereas I, using my IPv4 knowledge, was using global addresses of routing targets. V6 routing now requires a remote link local address combined with a local interface name to accomplish a connection. Once I applied the necessary digital band-aids to my VPN configuration scripts, my LAN-wide IPv6 connectivity returned!

    IPv6 addresses from Spectrum are not required to get this working, so the cat was up a tree, but just not this tree 😊

This discussion has been closed.

Categories