dhcpcd-discuss

Hi

On 23/01/2015 08:42, Giorgio wrote:
> thanks for the fix, I've just verified things works now as expected.

Yay


> My workaround was to build dhcpcd without ipv6 (--disable-ipv6),
> I've also tested calling the daemon with '-4' to force ipv4 only
> but it has the drawback that it adds a '-4' to the pid file and
> to kill it back you have to issue a:
> 
> # dhcpcd -k eth0:whatever-4
> 
> that's an inconvenient asymmetry is the calls...

You get the same problem when using -6, but in reverse.
Some people asked for the feature so they could control each protocol
independently.

> I'm not an expert on dhcp or even ipv6; could you please explain,
> shortly and
> without too many technical details, what kind of problems could arise when
> 'IPV6 autoconf' is 'running on each of them'.

dhcpcd keeps track of the state of each address on the interface.
Each instance will be adding and tracking the same IPv6 address from
each other. The code *should* be fine, but this is a scenario I've never
tested so I'm just saying it *might* go horribly wrong!
You don't appear to have any IPv6 so there's not much to do at this point.

Some IPv4 tracking is done as well, but because you're forcing static
it's a non issue.

Roy