Trouble switching from he.net to spectrum native v6
-
Solved: The problem was I still had the old he.net interface up and that was still the default v6 gateway
-
What prefix delegation are you requesting? This would be found on the WAN interface. Not sure what spectrum is giving. I'd either call them and get frustrated by the answer, "IPv-what?" or start at /56.
While you are there enable Start DHCP6 client in debug mode. That way you can search the DHCP logs for command dhcp6c and get a better idea of what's going on. It does not add a lot of extra logging but it is pretty useful.
-
I'm only requesting a single 64 as that was all I could get working in the past
-
I'm only requesting a single 64 as that was all I could get working in the past
Once you get it going, it's easy to request a larger prefix.
-
Once you get it going, it's easy to request a larger prefix.
The only problem is I still haven't got it going and even if I did I'm pretty sure they don't let you request a bigger one.
-
Once you get it going, it's easy to request a larger prefix.
The only problem is I still haven't got it going and even if I did I'm pretty sure they don't let you request a bigger one.
Why wouldn't they? I can change mine at will. The request is made by pfSense, according to the value you select.
-
Note also that you may have issues with IPv6 through Spectrum if someone has a spectrum voice phone on the local spectrum network outside your premises as per this post:
[–]fossicker
[+1] 3 points 4 days ago
tl&dr If you have separate Spectrum Data & Voice modems, native IPv6 is not supported on the data modem.I have had the same problem with Spectrum Business Class on a ARRIS DOCSIS 3.0 Touchstone Residential Gateway HW_REV: 5 VENDOR: Arris Interactive, L.L.C. BOOTR: 2.2.0.45 SW_REV: 9.1.103J6TW2.SIP.PC20.TW MODEL: DG1670A~~~~
also Spectrum Voice via a separate Voice modem.
In my case the data modem reboots were both random and non-random. I could reproduce a data modem reboot whenever an incoming voice call was processed by the voice modem. And the data modem also rebooted spontaneously on its own it seemed. Note that I was running native IPv6 on pfsense 2.4.1 and pulling a prefix successfully & LAN Track Interface.
The reboots stopped when I disabled IPv6 on the data modem and also pfsense WAN (= ipv4-only). Spectrum tech replaced modems three times and also ran a separate construction coax cable to the pole for the voice modem. Finally got through to the Spectrum NOC and was told that the Voice product is entirely IPv6 and native IPv6 is not supported on the data modem. This is true even if you don't have Voice but other customers do have Voice on the same cable segment – such that with native IPv6 enabled on a data modem, inbound Voice calls to any Voice customers on the same coax segment will bounce data modems. I even tested this at a neighbor's with Spectrum Residential and separate voice and data modems using a Ubiquiti Amplifi router with IPv6 enabled - data modem bounced on incoming Voice call AND when I called my own Voice number up the street.
Needing IPv6 for work, I set up a Hurricane Electric tunnel without issue.
(I gave up and just went back to tunnelbroker.)
-
Oh WOW. This exactly explains what I was seeing on my network. IPv6 would work fine for a while, and then boom data would bounce.
That doesn't make sense. If a phone was interfering with the modem, it would affect both IPv4 & IPv6.
-
I don't have voice service with them. The thing Is I can't even get v6 service working at all whereas that subreddit seems to indicate that it temporarily breaks it.
-
That doesn't make sense. If a phone was interfering with the modem, it would affect both IPv4 & IPv6.
You don't seem to appreciate how amazingly incompetent Time Warner Cable (now Spectrum) can be.
Their IPv6 DNS server they provide to residential customers is so many hops away from the actual customer modem that most requests time out.
Their billing department tried to sell me IPv6 as an add-on package. Like I was buying cable TV and they were selling more channels or something.
I have no trouble at all believing that they've screwed up when rolling out IPv6 data-versus-voice. Their service should be rolled out… of the building, across the parking lot, and into the dumpster.
