dhcpcd-discuss

Re: Late start for IPv6

Jouke Witteveen

Mon Apr 28 21:04:09 2014

On Mon, Apr 28, 2014 at 2:16 PM, Roy Marples <roy@xxxxxxxxxxxx> wrote:
> On 28/04/2014 10:28, Jouke Witteveen wrote:
>>
>> I (netctl at least) like to start my dhcp client separately for IPv4
>> and IPv6. Is there a possibility to tell a running 'dhcpcd -4'
>> instance to also take on IPv6, transforming it into an ordinary
>> 'dhcpcd' instance? Starting 'dhcpcd -6' on an interface that has a
>> running 'dhcpcd -4' instance fails (already running).
>
> This is not currently possible.
> Why would you (or netctl) want to do this?
>

In netctl, IPv4 and IPv6 are configured separately. In principle,
users could choose to use a different dhcp client for both versions of
the IP. When netctl goes through the IPv4 configuration stage, it
might start dhcpcd for IPv4. Later, in the IPv6 stage, it might want
to start dhcpcd for IPv6. If the client would have been dhclient in
both cases, this means there will be two instances of dhclient
running. One for the IPv4 address and one for the IPv6 address. These
instances can be tinkered with independently. For dhcpcd, it would be
nice if there was some form of introspection possible to allow IPv6 to
be added to the responsibilities of a running IPv4 instance.

If you find this approach is flawed to begin with, that is okay.
However, dhcpcd itself has a rather clean separation of the
implementation on both protocols, so my request might not be too hard
to implement (although I couldn't see a trivial fix).

Best,
- Jouke

Follow-Ups:
Re: Late start for IPv6Roy Marples
References:
Late start for IPv6Jouke Witteveen
Re: Late start for IPv6Roy Marples
Archive administrator: postmaster@marples.name