[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55DCFFB2.1030100@cumulusnetworks.com>
Date: Tue, 25 Aug 2015 16:52:18 -0700
From: David Ahern <dsa@...ulusnetworks.com>
To: Sowmini Varadhan <sowmini05@...il.com>,
Florian Fainelli <f.fainelli@...il.com>
CC: netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>, andrew@...n.ch,
linux@...ck-us.net,
Jiří Pírko <jiri@...nulli.us>,
sfeldma@...il.com
Subject: Re: [PATCH RFC 0/5] net: L2 only interfaces
On 8/25/15 4:44 PM, Sowmini Varadhan wrote:
> On Tue, Aug 25, 2015 at 3:50 PM, Florian Fainelli <f.fainelli@...il.com> wrote:
>> Hi all,
>>
>> This patch series implements a L2 only interface concept which basically denies
>> any kind of IP address configuration on these interfaces, but still allows them
>> to be used as configuration end-points to keep using ethtool and friends.
>>
>
> This is a very interesting idea. A few questions/thoughts: will there
> be any eventual restrictions on which types interfaces can be L2_ONLY?
> Ideally, it should be possible to let interfaces wink in/out of L2 only
> state administratively (as can be done on a typical router, after unwinding
> existing config as needed)
>
> I'm assuming something will prevent an L2-only interface from being
> part of a vrf.
The VRF driver can check the device when the enslave request happens.
--
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