[ovs-discuss] VXLAN tunnels and routing

Jesse Gross jesse at nicira.com
Sun Dec 21 20:40:29 UTC 2014


Linux, signaled to do so by OVS.

On Sunday, December 21, 2014, Tal Yaniv <Tal.Yaniv at contextream.com> wrote:

> 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:jesse at nicira.com <javascript:;>]
> Sent: Sunday, December 21, 2014 17:48
> To: Tal Yaniv
> Cc: discuss at openvswitch.org <javascript:;>
> Subject: Re: [ovs-discuss] VXLAN tunnels and routing
>
> On Sun, Dec 21, 2014 at 5:39 AM, Tal Yaniv <Tal.Yaniv at contextream.com
> <javascript:;>> 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 at openvswitch.org <javascript:;>
> http://openvswitch.org/mailman/listinfo/discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20141221/bc1be765/attachment-0002.html>


More information about the discuss mailing list