Ipv6 comcast

jcyr

Dummynet does not support rate/limiting per mac address. It is a layer three pipe.

awesomekyle

I'm having the same issue with my Comcast IPv6. I used to use an Airport Extreme as my router and connected directly to my modem from two different PCs and I've had perfect native IPv6 compatibility for months now (I'm in Oregon). Today I tried using pfSense, but it's only working for IPV4.

I've tried every option I can think of under my WAN connection, but nothing seems to change it. The problem is that pfSense just doesn't get an IPv6 address from Comcast while my other router has no problem.

I'm not sure if this is related, but every other router and computer I've tried has always gotten a 24.21.XXX.XXX IP address. pfSense is getting me a 76.27.XXX.XXX IP address. My connection still works fine (hence being able to post this), I just thought that it was odd.

chpalmer

@awesomekyle:

I'm having the same issue with my Comcast IPv6.
I've tried has always gotten a 24.21.XXX.XXX IP address. pfSense is getting me a 76.27.XXX.XXX IP address.

When we replace the SMC modems with Mororola 6141's on several Comcast commercial account customers we got the opposite. We now have several customers on the 24.19.x.x range from the 76.x.x.x range… We were told ahead of time this would happen actually.

Which modem are you using? Gateway modem in bridge mode by chance?

edit- Ive only set on WAN-

IPv6 Configuration Type= DHCP6
DHCPv6 Prefix Delegation size 64

Send IPv6 prefix hint- checked.

awesomekyle

I'm using an Arris TG862G.

Per a suggestion on Reddit, I tried changing the prefix to 56 along with sending the prefix hint and I actually got an IPv6 address for my WAN interface. However, my clients weren't getting any addresses. I rebooted pfSense to see if that would fix it, but when I did, I lost my IPv6 address. My settings haven't changed, and I've tried putting it back to /64, but still no IPv6 address.

chpalmer

@awesomekyle:

I'm using an Arris TG862G.

Per a suggestion on Reddit, I tried changing the prefix to 56 along with sending the prefix hint and I actually got an IPv6 address for my WAN interface. However, my clients weren't getting any addresses. I rebooted pfSense to see if that would fix it, but when I did, I lost my IPv6 address. My settings haven't changed, and I've tried putting it back to /64, but still no IPv6 address.

Did you set your LAN port IPv6 to track interface? Then under "track IPv6 interface" lower on the LAN page- track WAN and 0 should work.

On WAN I also have block bogons unchecked. Check your LAN firewall rules for an IPv6 outgoing rule.

WANpage.jpg_thumb

priller

@awesomekyle:

I'm using an Arris TG862G.

Per a suggestion on Reddit, I tried changing the prefix to 56 along with sending the prefix hint and I actually got an IPv6 address for my WAN interface.

The TG862G is a gateway (router), not just a modem. You had Comcast put it in bridge mode? If not, that would explain a WAN address on pfSense and nothing else. In order to get a DHCP-PD addressing for the LAN, pfSense needs to talk directly to Comcast and that requires the TG862G to be put into bridge mode by Comcast.

You mentioned the Airport Extreme, is that truly in router mode or is it operating in bridge mode?

Darkk

@chpalmer:

@awesomekyle:

I'm using an Arris TG862G.

Per a suggestion on Reddit, I tried changing the prefix to 56 along with sending the prefix hint and I actually got an IPv6 address for my WAN interface. However, my clients weren't getting any addresses. I rebooted pfSense to see if that would fix it, but when I did, I lost my IPv6 address. My settings haven't changed, and I've tried putting it back to /64, but still no IPv6 address.

Did you set your LAN port IPv6 to track interface? Then under "track IPv6 interface" lower on the LAN page- track WAN and 0 should work.

On WAN I also have block bogons unchecked. Check your LAN firewall rules for an IPv6 outgoing rule.

Thanks for the screenshot. I finally got mine working perfectly now. Although have to try it running Windows 7 as I use Kubuntu 13.10 all the time now. I did enable the privacy using "prefer public address" in Kubuntu.

EDIT: Also, I do have Block bogon networks checked on the WAN so it's working fine with it.

razzfazz

Doesn't "prefer public address" _dis_able the privacy extensions?

Darkk

Well, either that or it's disabled? See screenshot. I will have to research this.

EDIT: I tried to use 'prefer temporary address' setting and it disables the privacy….Hmmm

IPV6_Kubuntu.png_thumb

Darkk

Seems I have to figure out how to keep Kubuntu from using my PC's MAC address in the IPv6 address space. It's not PfSense issue, it's Linux so I have to fix it.

EDIT: After some Googling found the answer. Have to add net.ipv6.conf.eth0.use_tempaddr=2 in the /etc/sysctl.conf which will force the privacy settings. The Kubuntu Network Manager GUI apparently can't change that setting. Bummer. No big deal. Long as I can change it in the config file then it's good. Have to keep eye on this since any network security updates may overwrite this. It's a known issue.

Ran a couple of IPv6 Test sites and it no longer showed my real MAC address. Yay!

razzfazz

It can change this setting; in fact, the corresponding option is right there in your screenshot: By selecting "prefer public address," you explicitly told it to use the SLAAC address (which contains your MAC) for outgoing connections; the setting you actually want is "prefer temporary address," which will use a randomly generated address (that even changes periodically) for outgoing connections. That is precisely what the IPv6 privacy extensions are.

Darkk

Yes that would be true and I did select it. However, when I go back into it says it's disabled so had to modify the file manually.

IPv6_NetworkStatus.png_thumb

cmb

Anyone who is still having problems with Comcast's native IPv6, please try a 2.1.1 snapshot, and post your experiences to the 2.1.1 board.
https://forum.pfsense.org/index.php/board,56.0.html

As with any snapshot builds, take care when using them. They're just automatically built with no testing. Using the "full backup" feature is always a good idea with snapshots, then you can easily revert back without reinstalling.

ropeguru

@cmb:

Anyone who is still having problems with Comcast's native IPv6, please try a 2.1.1 snapshot, and post your experiences to the 2.1.1 board.
https://forum.pfsense.org/index.php/board,56.0.html

As with any snapshot builds, take care when using them. They're just automatically built with no testing. Using the "full backup" feature is always a good idea with snapshots, then you can easily revert back without reinstalling.

Upgrading now to the January 25 build. Will let you know how it works. I was able to finally get my pfSense to hand out IPv6 address on the LAN but the WAN side was always trying to route across the link local address to the Comcast Netgear. From the insise I could ping6 my router LAN address and WAN address but could never get any further.

eri--

Give a try with a snapshot from late tomorrow since behaviour should be improved.