Comcast uses stateful DHCPv6 where it delegates a Identity Association (the /128 for your external interface) and a Prefix Delegation which can be used on your internal network. Comcast will allocate a PD of up to a /60 which could give you up to 16 /64 site level aggregation (SLAs).
Right now I can o all of this on FreeBSD using a third party package (KAME DHCPv6). I belive the SRX can support it based on this KB: http://kb.juniper.net/InfoCenter/index?page=content&id=KB30509&actp=search Let me know how it goes. Jonathan ________________________________ From: juniper-nsp <[email protected]> on behalf of Chris Adams <[email protected]> Sent: Saturday, July 2, 2016 8:15 AM To: [email protected] Subject: Re: [j-nsp] Anybody have an SRX working with Comcast DHCP v4 and v6? Once upon a time, Aaron Dewell <[email protected]> said: > I attempted to make this work on an SRX210 running 12.1X46-D30 with TWC. The > inherent issue was that Junos will only accept multiples of 16 bit-boundaries > as a dhcpv6 client, and /56 (as TWC assigns) is not accepted. > > So it's less about your settings and more about the known PR, assuming that > Comcast is delegating a /56 as TWC does. For residential, I think the largest Comcast assigns by PD is /60. However, it is up to you to set the request size; DHCPv6 has a field for that (IIRC by default you only get a /64 from Comcast). I see (on OpenWRT, not JUNOS) a /128 assigned to the WAN interface and a DHCPv6 PD /60, which OpenWRT then carves up for the local networks. -- Chris Adams <[email protected]> _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
