[ovs-discuss] Forward VxLAN packets in network namespace?

Jesse Gross jesse at nicira.com
Tue Sep 8 06:36:53 UTC 2015


On Monday, September 7, 2015, Xiao Liang (xiaolia) <xiaolia at cisco.com>
wrote:

>
> > -----Original Message-----
> > From: Jesse Gross [mailto:jesse at nicira.com <javascript:;>]
> > Sent: Monday, September 07, 2015 21:55
> > To: Xiao Liang (xiaolia)
> > Cc: discuss at openvswitch.org <javascript:;>
> > Subject: Re: [ovs-discuss] Forward VxLAN packets in network namespace?
> >
> > On Monday, September 7, 2015, Xiao Liang (xiaolia) <xiaolia at cisco.com
> <javascript:;>>
> > wrote:
> >
> >
> >       Hi,
> >
> >       The problem is that I want to add a VxLAN port to OVS bridge and
> let
> > the tunnel packets be routed in a particular netns.
> >
> >       In VxLAN vport code I found that the namespace of the tunnel sock
> is
> > inherited from dp. I could add a dp by "ip netns exec ns1 ovs-dpctl
> add-dp
> > br1", but how can I use it then? I've also tried "ip netns exec ns1
> ovs-vsctl
> > add-br br1" and "ip link set br1 netns ns1", but seems not work.
> >
> >
> >
> > You can only change the namespace of OVS as whole. To do that you, you
> > should start ovs-vswitchd in that namespace. If you want to route tunnel
> > packets to a different namespace, you'll have to do that through the
> routing
> > table.
>
> Thanks! If I start multiple ovs-vswitchd each in a different namespace,
> need I also start multiple ovsdb?
>
>
Yes, since they are operating as independent switches.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20150907/3d552b2a/attachment-0002.html>


More information about the discuss mailing list