[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB=NE6Uf63XAAi_Sy5iSy2sjfNdWd9QsPECMBVBrUX9z4_L5-g@mail.gmail.com>
Date: Mon, 24 Feb 2014 12:33:35 -0800
From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
To: Dan Williams <dcbw@...hat.com>
Cc: Zoltan Kiss <zoltan.kiss@...rix.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
xen-devel@...ts.xenproject.org, kvm@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>
Subject: Re: [RFC v2 2/4] net: enables interface option to skip IP
On Mon, Feb 24, 2014 at 10:22 AM, Dan Williams <dcbw@...hat.com> wrote:
> My use-case would simply be to have an analogue for the disable_ipv6
> case. In the future I expect more people will want to disable IPv4 as
> they move to IPv6. If you don't have something like disable_ipv4, then
> there's no way to ensure that some random program or something doesn't
> set up IPv4 stuff that you don't want.
>
> Same thing for IPv6; some people really don't want IPv6 enabled on an
> interface no matter what; they don't want an IPv6LL address assigned,
> they don't want kernel SLAAC, they want to ensure that *nothing*
> IPv6-related gets done for that interface. The same can be true for
> IPv4, but we don't have a way of doing that right now.
I'll add this to my queue.
Luis
--
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