dhcpcd-discuss

On 22/06/2014 14:37, Roy Marples wrote:
> On 22/06/2014 11:00, Roy Marples wrote:
>
> > Well, it all sounds bogus to me.
> > From the one of your client machines, can you provide a traceroute6 to
> > a public IPv6 address such as roy.marples.name?
>
> So I did some research and found this:
>
> Comcast will assign a /128 for their on-link network. Comcast will
> then assign you a routed block (/64 for now, could be /60 or /56 in
> the future). The routed block will be routed to your on-link network
> address.
>
> Which explains why you need this.
>
> > > Being able to request any combination of ia_XX entries, or at least
> > > ia_na and ia_pd seem necessary.
> >
> > And not that easy to implement correctly either.
> > There is a work in progress document to make it easier, but it's not a 
> > RFC yet.
> > https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/?include_text=1
> >
> > Once that becomes a RFC, this would be much easier to do in dhcpcd.
> > But if you read the emails through underneath it, it should not be
> > needed because you get workable routable addresses via PD by itself.
> > So is comcast doing something really odd?
>
> I'll see what I can do about implementing this, maybe comcast will work 
> it it.

This has now been implemented.
http://roy.marples.name/projects/dhcpcd/ci/11451d70930a170b2ebaf36c28ca718f33d426e5?sbs=0
http://roy.marples.name/projects/dhcpcd/ci/49bc4c095d5f5a7dc49da75ad941097bd5551d0e?sbs=0

May not apply cleanly to dhcpcd-6.4.0, you may need to get a fossil 
snapshot.

Could do with some testing. I tested it with isc-dhcpd-4.2.5-P1 and it 
seemed to work fine.
Let me know how it works for you and ComCast!

Thanks

Roy