Comcast native ipv6 for network devices.
-
So my understanding is that comcast has started rolling out delegated prefixes for networking devices.
http://blog.comcast.com/2012/04/ipv6-deployment-technology.html
I believe, but not 100% sure that I am in a test area. I can get a ipv6 address on my wan if I set it to dhcp6 - this hands out ipv6 dns, etc. But it seems I only get a /128 so not sure if still just limited to single devices?
Is anyone using pfsense with comcast native ipv6, not talking a 6to4 setup. In the Schaumburg, IL area that knows if we can use native ipv6 with networking devices with comcast yet?
I am currently using an he tunnel on 2.1 and this works fine. But would like to move to native from my ISP vs the tunnel - but just not clear if supported yet in my area or how to set it up so that I get an ipv6 on my lan interface for use on my local network.
I found this
http://www.tiven.org/networking/native-ipv6-networking-with-pfsensebut this says to use a link-local address of fe80::1 /64 – is that correct? So the lan interface of pfsense will not get a global address? But clients on the network will? How would use work with static addresses in this case?
-
Iirc Comcast is doing a single /64 for the LAN, and yes the WAN is a /128, that's because of the DHCP6 lease.
Select dhcp6 on the WAN, set the prefix delegation size to 64 bits.
Go to the LAN interface, for IPv6 select "Track Interface". Set it to interface "WAN" and the network prefix is always 0 for you.That should basically be it. Let me know how that works out. Really Curious.
-
Not going to do that remote for sure ;) Don't want to lock myself out - but give it a try when I get home for sure and let you know.
Thanks!
edit: Well that seemed to work.. But couldn't not get to any ipv6 address once I removed the tunnel. Going to bring up a clean vm to play with the native stuff.
-
Should just work, could well be some left over config from the tunnel or one of the clients not releasing the old tunnel prefix.
Reboot pfSense, reboot the clients and see if that fixes it.There have been a few cases where some clients will not release the old prefix eventhough we Advertise the old prefix as being discontinued. It would still be valid for about 3 minutes after that.
-
I did reboot after removed the tunnel.
Just going to play with it on a clean vm.. If that all works out, then just stay with that vm, etc.
-
Ok finally got around to playing with this with a clean vm, no he.net tunnel setup before, etc. I grabbed the latest ova and booted right up. I get ipv6 on wan, and the tracking gives me ipv6 on lan.
But does not seem to find a ipv6 default route?
Here are some screen shots of route table, console showing IPv6 addresses and mask and gateway widget showing doesn't have one, etc.
I just run an gitsync this morning as well, just a few minutes ago and reboot.. How do I get it to get default ipv6 route?
-
Ok still not working??? WTF? I believe that comcast has enabled ipv6 everywhere. Atleast in chicago this shows it is enabled
https://maps.google.com/maps/ms?msid=213069112737090935874.0004c1d17d71a22c5d721&msa=0&iwloc=0004c1d17d788f5a044edUpdated my comcast ipv6 vm to the latest, its gets an ipv6 on its wan. But even pfsense can not get anywhere via ipv6 when using ipv6 from comcast. HE works great. Comcast native not so much ;)
Any help - more than happy to let someone in that could take a look remotely to why not getting any default route for ipv6?
Ok maybe its not really enabled. Shouldn't I be seeing RA on my wan interface with a simple tcpdump command
example
tcpdump -n -i em1 -vv ip6not getting nothing.. Seems odd?
-
Look like that is a crowdsourced map of deployment, which might be faulty.
I see other threads in a forum I frequent where people claim to have IPv6 but it turned out to be a link-local.
If you do not see a RA on the WAN you don't have to try. They support both SLAAC and DHCP6 on the WAN so yes, you should see atleast RA messags.
-
yeah not seeing those.. Guess not available here for routers yet.
-
tcpdump -n -i em1 -vv ip6
Unless I'm missing something, those screenshots above show you with a DHCPv6 address. Also you're running tcpdump on the wrong interface according to those screenshots. It should be em0.
Comcast's gateway should be the LL address on the interfaces page.
-
No, that looks more like a stateless autoconf address, you get that one for free, but that would atleast imply that something is advertising.
I just setup a test box here and it worked, I did need to enter atleast 0 in the prefix id field on the LAN interface for the "Track interface WAN" section before it configured a prefix on the LAN. After a reboot nonetheless.
Still need to polish those edges.
-
No, that looks more like a stateless autoconf address, you get that one for free, but that would atleast imply that something is advertising.
Maybe one could add the radvdump binary to pfsense (or have it as a package) as I assume it could help a few to ease debugging their IPv6 setup?
-
No, that looks more like a stateless autoconf address, you get that one for free, but that would atleast imply that something is advertising.
It's actually not. Comcast RAs have the managed flag set on them. Mine looks the same and it's not SLAAC.
Also 2601::/28 is Comcast's prefix they're assigning via PD.
My guess is somehow the LL gateway isn't being added. It would really help if the OP could post a screenshot of his interface page.
For example, mine is: Gateway IPv6 fe80::201:5cff:fe32:1481
-
Maybe johnpoz is willing to give me access to his install for debugging?
-
Just to update with more info as to what a Comcast deployment is.
13:54:58.045607 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 80) fe80::201:5cff:fe32:1481 > ff02::1: ICMP6, router advertisement, length 80
hop limit 0, Flags [managed, other stateful], pref medium, router lifetime 1800s, reachable time 30000s, retrans time 1000s[ndp opt]Screenshot of interfaces: http://willscorner.net/tmp/comcastic.png
-
Yeah, that screenshot looks healthy.
-
Yeah more than willing to give access to take a look.. Just PM me when would be good time for you to access, and I can send you the info to remote in.
I have got a comcast guy on another forum checking for sure if should be available in my area.
As to screen shots and what em – they might of swapped because I was using 2 different vms in testing this. I had a clean vm that wasn't working and then was playing with it again on my normal vm. So those 2 vms might be swapped for which em is wan and which is lan, etc. Would have to double check that.
edit:
So if you see in the screenshots I posted I was getting Ips -- but just couldn't get anywhere, I didn't see a default route for ipv6. But looking forward to your PM on your schedule - I should be available tonight, few hours from now to switch it over to my clean install with no tunnel setup -- can let you in for sure to take a look. Would really really appreciate that!If you have time now I could remotely turn on remote access and let you in to current setup with HE tunnel setup, etc. And you could play with that. Don't care too much if you break the tunnel setup. Doesn't matter if loose the tunnel that is currently setup, would like to go native anyway ;)
edit2: Got your PM, thanks once I hear back from the comcast guy that its suppose to be there I will let you know. But what I am thinking is it's not there yet?
So this is my normal vm, I turned off the HE tunnel. Updated to the latest and greatest snap
2.1-BETA0 (i386)
built on Tue Jun 19 20:53:56 EDT 2012
FreeBSD 8.3-RELEASE-p3I then run gitsysnc this morning to be sure. Deleted my HE tunnel stuff, set wan to dhcp6, prefix delegation 64. Then set Lan to track and 0 for prefix ID. Rebooted.
As you can see from screenshot I get a /128 and shows a /64 on my lan.. But just don't get a route out on ipv6 -- so I have highlighted that yes my wan is em1, and let a tcpdump -i em1 -vv ip6 run for like 5 minutes or so and just don't see anything! I should be seeing RA should I not? There should be some in a 5 minute period I would think ;)
So my guess is something is not turned on at my isp for native to work yet for me. Once I hear back from the comcast guy on another forum that is checking with my modem mac and still nothing working I will let you know and more than happy to let you in. Happy to let you in now if you want.
-
I edited my last post, but does not seem to have bumped the time on the thread. So bumpity bump ;)
-
johnpoz,
Reach out in the Comcast forums on dslreports.com. It looks like they've set up DHCPv6 without RA. Just checking though, you've got a DOCSIS3 modem, right?
-
Yup SB6120, and have PM out to netdog on that site, he responded already once - but seems I only game him the CMTS-MAC, when he needed the CM-MAC? So now I have sent him everything I could see from the modem with any sort of mac in it ;)
I thought he would need the CMTS-MAC to see if ipv6 was enabled on my connection, this is what my modem connects too right?
