[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140225.161817.1623503840238501415.davem@davemloft.net>
Date: Tue, 25 Feb 2014 16:18:17 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: dcbw@...hat.com
Cc: mcgrof@...not-panic.com, zoltan.kiss@...rix.com,
netdev@...r.kernel.org, xen-devel@...ts.xenproject.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
kaber@...sh.net
Subject: Re: [RFC v2 2/4] net: enables interface option to skip IP
From: Dan Williams <dcbw@...hat.com>
Date: Tue, 25 Feb 2014 15:07:00 -0600
> Also, disable_ipv4 signals *intent*, which is distinct from current
> state.
>
> Does an interface without an IPv4 address mean that the user wished it
> not to have one?
>
> Or does it mean that DHCP hasn't started yet (but is supposed to), or
> failed, or something hasn't gotten around to assigning an address yet?
>
> disable_ipv4 lets you distinguish between these two cases, the same way
> disable_ipv6 does.
Intent only matters on the kernel side if the kernel automatically
assigns addresses to interfaces which have been brought up like ipv6
does.
Since it does not do this for ipv4, this can be handled entirely in
userspace.
It is not a valid argument to say that a rogue dhcp might run on
the machine and configure an ipv4 address. That's the admin's
responsibility, and still a user side problem. A "rogue" program
could just as equally turn the theoretical disable_ipv4 off too.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists