Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I want to do this, but Comcast's prefix isn't stable, I get a different one every time my lease renews, which means it is impossible to have a static IP for all my network devices, since neither pfSense nor OPNsense support NPTv6 to a dynamic prefix.


It would be really bad for business if Comcast started assigning static addresses for all their customers. The doxxing villains would surely take advantage of a world in which same address == same person.

If some dodgy site gets a visitor from a Comcast netblock they would know that, should they ever de-anonymise the address, the John at the other end has zero plausible deniability to fall back on.

That being said, there’s no excuse for Comcast to at least give you the option of a static /48. I see that they themselves have a /20. That alone is enough for a /48 for each of 268 million customers (8x their current userbase) who would each be able to route 65k broadcast domains (/64 subjects.)


I've been using IPv6 on Comcast for years now, and my prefix has been stable during that entire time. Double check that your DHCP client is not sending a new UUID for each lease request. The UUID should be stable so that the DHCP server knows to give you the same prefix each time.

I've got a /60 with multiple VLAN's running without issues.


I assume you mean DUID, and yes, it's fixed.

Comcast's IPv6 behavior varies depending on where you live.


> neither pfSense nor OPNsense support NPTv6 to a dynamic prefix.

If you wish to keep track, I believe this is where pfSense is working on this:

* https://redmine.pfsense.org/issues/4881


A 6 year old bug, that depends on a 5 year old bug.

I won't hold my breath!


That is pretty dreadful. You may be able to use RFC 4193 (ULA) addresses to get some stability but then what you get is a sort of buggered up IPv4 experience with really long addresses.

It would make a worthy challenge, the struggle would be legendary etc 8)


> the struggle would be legendary

You just assign a ULA address to an interface and that's it. There is no "struggle."


Quite. I was making a rather bad joke.


Hmm yes I have several static prefixes, so that helps. I'm in the EU though...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: