[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53314FDF.2060205@6wind.com>
Date: Tue, 25 Mar 2014 10:43:59 +0100
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: ratheesh kannoth <ratheesh.ksz@...il.com>
CC: Jesse Gross <jesse@...ira.com>, netdev <netdev@...r.kernel.org>
Subject: Re: openvswitch question
Le 21/03/2014 16:15, ratheesh kannoth a écrit :
> On Fri, Mar 21, 2014 at 3:20 PM, Nicolas Dichtel
> <nicolas.dichtel@...nd.com> wrote:
>> Stop me if I'm wrong, but there may be a difference with netns, the
>> netdevice
>> can be in a different netns than the ovs port.
>
> No. below command show no name space.
>
> ip netns list
Sure, you have to create one first.
But you can start ovs in the current netns and move the interface to another
netns after that.
Then, you will show the ovs port in the initial netns and the network dev in the
other netns.
--
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