dhcpcd-discuss

(I forgot to CC the mailist, sorry about that)

Wonderful! Thank you so much for the hard work. No need to hurry as this is
not critically important at least for me, b/c I can use noipv4/6 to realize
the same result.

By the way, I noticed that when PD activated an interface's ipv6 stack, it
will automatically do the ipv4 stack as well. I am not sure if this is the
typical desired application scenario but at least for me, I would prefer PD
to touch ipv6 only and leave ipv4 alone because PD is strictly speaking an
ipv6-only thing. If a hypothetical user would "disable an interface at
first, but wouldn't mind using PD to assign ipv6 address on it using
dhcpcd", then I think most likely that user would like to avoid ipv4 on
this interface at all.

But this is just my thoughts and may not of course represent most of the
users :)

Thank you again for the hard work!

Peng

On Wed, Feb 3, 2016 at 9:47 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:

> Hi Peng
>
> On 03/02/2016 12:28, Peng Shao wrote:
> > Hi Roy, thanks for the work. Sorry it is still not working :(
> >
> > I did the followings:
> > 1. download the tarball,
> > 2. configure and make
> > 3. disable dhcpcd service in systemd then reboot to test in clean
> > environment
> > 4. use the following conf to test:
> >
> > /root/dhcp.conf
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~`
> > debug
> > slaac private # My ISP only answers to me if I have this enabled, a
> > little weird.
> > allowinterfaces enp4s0
> > noipv6rs
> > interface enp4s0
> > ipv6rs
> > ia_na 1
> > ia_pd 2/::/56 enp6s0/1/64 enp8s0/2/64 enp9s0/3/64
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > And there is the output, the first interface (enp6s0) is still ignored:
>
> I've replicated the problem and am now working on a fix in my very
> limited free time.
>
> Roy
>