[ovs-discuss] Question on tunnel interfaces

[Padmanabhan Krishnan]

A quick follow-up on this.Even for the reverse traffic, does the kernel hand over all traffic received on the interface (173.x.. subnet attached to eth2) to "br-tun" which will decapsulate the frame, if it came in with the proper tunnel id? I am assuming OVS cannot register with the kernel to hand over only tunnel frames, right? 
Thanks,Paddu

     On Monday, April 27, 2015 1:11 PM, Jesse Gross <jesse at nicira.com> wrote:
   

 On Mon, Apr 27, 2015 at 12:44 PM, Padmanabhan Krishnan <kprad1 at yahoo.com> wrote:
> Thanks a lot Ben and Jesse.
>
> Just wanted to clarify, from your statements:
>
> “OVS simply hands the packet over to the kernel IP stack.”
>
> "After encapsulation, OVS turns the packet over to the kernel TCP/IP
> Stack"
>
> Is the above (handling the frame to kernel to do the routing) a special
> functionality of the tunnel bridge/port?
>
> For example, if a VM connected to a regular OVS bridge (br-int) sends a
> frame destined to a 173.x.. subnet (attached to eth2), i assume OVS will
> bridge the frame and not hand it over to the kernel, right?

Yes, this is specific to tunnel ports because outputting to a tunnel
implies the use of the IP stack. There is no implicit routing for
other types of devices.

  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20150429/f8dfb520/attachment-0002.html>