dhcpcd-discuss

On Mon, May 5, 2014 at 9:10 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:
> On 29/04/2014 14:56, Jouke Witteveen wrote:
>>
>> On Tue, Apr 29, 2014 at 1:09 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:
>>>
>>> On 28/04/2014 22:03, Jouke Witteveen wrote:
>>>>
>>>>
>>>> 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.

> Would netctl be happy with this?
>
> dhcpcd --per-protocol -4 eth0
> dhcpcd --per-protocol -6 eth0
>
> dhcpcd --per-protocol -4 -x eth0
> dhcpcd --per-protocol -6 -x eth0
>
> Would create the pidfiles:
> /var/run/dhcpcd-eth0.pid
> /var/run/dhcpcd-eth0.6.pid
>
> That would be fairly trivial to implement.
> Let me know

That would be very nice!

What would happen in this case?

dhcpcd --per-protocol -4 eth0
dhcpcd --per-protocol -6 eth0
dhcpcd -x eth0

I'd say it would be best to either kill both or kill none and error.
This is not relevant for netctl, but could be relevant for someone
else out there.

Thanks,
- Jouke