Thanks Jesse, But it is still not clear to me, which module actually adds the tunnel header to the packet? Is it the OVS or the Linux?
Best Regards, Tal -----Original Message----- From: Jesse Gross [mailto:je...@nicira.com] Sent: Sunday, December 21, 2014 17:48 To: Tal Yaniv Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] VXLAN tunnels and routing On Sun, Dec 21, 2014 at 5:39 AM, Tal Yaniv <tal.ya...@contextream.com> wrote: > Hi, > > > > I’d like Linux network stack to handle my routing, if I define an OVS > bridge, with several interfaces (eth0-eth2) , which are on different > networks. > > Plus, several VXLAN ports on the same bridge. > > And I define a flow with a VXLAN encapsulation action and output to > LOCAL (meaning to the Linux network stack). You need to output to a VXLAN port. There is no VXLAN action, only one to set tunnel parameters such as IP address. Once you send the packet to the tunnel port, it will be routed by the Linux stack as you describe. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
