Re: [v6ops] Please review the No IPv4 draft

[Simon Perreault <[e-mail]>]

Le 2014-04-14 16:12, Gert Doering a écrit :
>>>> $ grep "option no-ipv4" /var/db/dhclient6.leases.eth0 && pkill dhclient
>>>>
>>>> - Is that too hard to implement?
>>>
>>> Yes.  My DHCP client is called "dhcpcd".  Nick's might be "pump".
>>
>> I'm sorry, I don't see your point.
> 
> There are at least 3 different IPv4 DHCP clients on "Unix", and the
> author and maintainer of the IPv6 DHCP client that is installed might
> not know which IPv4 DHCP client you're using.
> 
> So either there is a standard way to communicate this across, as in
> "all *IPv4* DHCP clients need to learn that", or it will fail in some
> scenarios, no matter what the IPv6 DHCP client maintainers do.

Ah I see what you mean.

I would not expect the DHCPv6 client to have any code added. It would be
the controlling "glue code" (e.g., NetworkManager, init scripts,
whatever) that would be modified.

> (Also, I'd consider "just kill a foreign process" to be very rude - and
> depending on the environment you're doing this in, it will be futile
> as well, because a "service manager" of some sort could just report an
> error, and restart the "failing" dhclient process).

Of course. The glue code would terminate the DHCPv4 client process in
the appropriate manner.

>>> To the contrary.  A network that does not provide IPv4 would want to set
>>> that option.  You might just not have public IPv4 here, because it's
>>> a zeroconfo network with only IPv4 link-local (169.254) addresses.
>>
>> I'm not following your reasoning, sorry.
> 
> More bluntly: what makes you think that a network that has no IPv4 has IPv6?

Because we absolutely don't care about other kinds of networks. We're
doing this so that IPv6 works better. We don't care about making IPv4
work better.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca