It works now. Thanks a lot.
> -----Original Message----- > From: Jesse Gross [mailto:je...@nicira.com] > Sent: Tuesday, September 08, 2015 14:37 > To: Xiao Liang (xiaolia) > Cc: discuss@openvswitch.org > Subject: Re: [ovs-discuss] Forward VxLAN packets in network namespace? > > On Monday, September 7, 2015, Xiao Liang (xiaolia) <xiao...@cisco.com> wrote: > > > -----Original Message----- > > From: Jesse Gross [mailto:je...@nicira.com] > > Sent: Monday, September 07, 2015 21:55 > > To: Xiao Liang (xiaolia) > > Cc: discuss@openvswitch.org > > Subject: Re: [ovs-discuss] Forward VxLAN packets in network namespace? > > > > On Monday, September 7, 2015, Xiao Liang (xiaolia) <xiao...@cisco.com> > > 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. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
