dhcpcd-discuss

On 21/06/2014 23:23, Robert White wrote:
> (Forgot to subscribe _before_ sending bug... please forgive the
> out-of-band responses. I've remedied the subscription issue. 8-)
>
> I applied both patches and the results were good. Thanks for the quick 
> patch!

:)

The important thing is that it's now working for you.

> NOTE: because of the way comcast works, if you put this into use you
> should regenerate/refresh your DUID by deleting /etc/dhcpcd.duid and
> then running dhcpcd --duid.  Comcast will keep giving you the previous
> ::/64 prefix if you use the previous DUID.

You could also release the old lease (dhcpcd -k while dhcpcd is 
running).
If that doesn't work (which it should) then yes regenerating the DUID is 
fine.
You could also change the IAID.

> I would make one thing more clear in the documentation.
>
> In the syntax ia_pd X interface0/identifier/prefix its not clear that
> "prefix" is the final desired prefix.
>
> In my first go I tired "ia_pd 3/::/60 int0/1/4" because the previous
> error messages were in the form "x:y:z:n::/64 + 1/4" so I thought the
> second prefix was added to the first. (I think the actual way it works
> is more correct, I was just confused by the "+" semantics in the error
> message.)
>
> It didn't take me long to figure out that I wanted
>
> ia_pd 3/::/60 intX/1/64 intY/2/64
>
> and so forth. It might be nice to add another example to the man page
> with potential yields. Particularly for something other than intN/X/64
> (say an intN/X/62 that might be further subdivided deeper within the
> site).

As you were confused AND found the solution, can you suggest 
improvements
to the man page and error message as it looks fairly clear to me?

Thanks

Roy