Ipv6 not working on comcast
-
Correct I'm borrowing 4 bits from the /64 which would only be 16 subnets (It was late last night when I was working on this). I am still missing the /61 subnet under WAN is anyone else seeing this? Is this by design? Also I have not been able to an IPv6 address working on more than one interface. Right now I am only trying to get a IPv6 working on my LAN and WiFi subnets but when I change the WAN PD to /63 and set the LAN prefix to 1 and the WiFi prefix to 0 I can not pull a IP on those interfaces. Has anyone else tried to get IPv6 working on more than one interface. Not sure if the problem is on the PfSense side or my ISP's side. I'm running 2.1-RC1 (amd64) built on Mon Aug 26 16:50:31 EDT 2013 FreeBSD 8.3-RELEASE-p10
-
Has anyone else tried to get IPv6 working on more than one interface.
Works just fine, though never tried with any similar weird subnets… /48 on WAN, /64 on LAN, WLAN etc.
-
Just checked with Engineering at Comcast and IA_PD is not supported in the NJ Philadelphia area yet. :'( They hope to bring the larger prefixes in the up coming months. I will update everyone when I find out more. (I guess this only effects you if you have Comcast and live in the NJ / Eastern PA area).
-
Works just fine, though never tried with any similar weird subnets… /48 on WAN, /64 on LAN, WLAN etc.
With Comcast?
-
They had rolled out support for /60 prefixes a while back, then apparently ran into issues with some CMTSs and removed that support again, supposedly to be re-enabled after some testing. That is the last I've been able to find online about this, so I was assuming the testing was still ongoing and /64 is still all we get for now.
-
Works just fine, though never tried with any similar weird subnets… /48 on WAN, /64 on LAN, WLAN etc.
With Comcast?
No, no Comcast… As suggested above, ISP issue most likely, nothing to do with pfsense.
-
It looks like Comcast has support for /60 most areas except for two major one which I can't tell you what they are. Philadelphia / Eastern PA and New Jersey is one major area and not sure what the other is. You can follow http://forums.comcast.com/t5/Home-Networking-Router-WiFi/IPv6-prefix-size-and-home-routing/td-p/1495933 There is a engineer there if you post on the main forum he may be able to help you out if you want to see if there is support in your area. He/she is very quick with their responses.
-
I finally managed to get a /60 delegated from Comcast and delegate parts of it to different subnets. Out of the box, this currently does not work, as Comcast will delegate a /64 by default unless a shorter prefix is explicitly requested via a prefix hint, and pfSense currently does not send such a hint.
I've added a switch to enable such hints; see pull request 792.
-
razzfazz what area of the Country do you live? I'm in the Northeast (Philly,NJ,NY). I would like to keep track of which areas are working for others who might be having issues.
Thanks,
-
SF Bay Area.
-
Also, pull request has been accepted, so the switch should turn up in the next snapshot.