[lkml]   [2014]   [Feb]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC v2 2/4] net: enables interface option to skip IP
From: Dan Williams <>
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

Since it does not do this for ipv4, this can be handled entirely in

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.

 \ /
  Last update: 2014-02-25 23:02    [W:0.152 / U:1.256 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site