When tracing the tunnel / vxlan path I figured this function gets used there, after the vxlan decap and re-injecting the packet into the ip stack. May be thats the only use case.
Thanks. On Fri, Jun 6, 2014 at 6:51 PM, Madhu Challa <[email protected]> wrote: > I have the following config > > b74843d3-1b4e-49a4-b169-0f6d85fb6260 > Bridge "br1" > Port "eth2" > Interface "eth2" > Port "br1" > Interface "br1" > type: internal > > and an ip address assigned to br1 > > br1 Link encap:Ethernet HWaddr 90:e2:ba:61:e7:44 > inet addr:13.1.1.2 Bcast:13.1.1.255 Mask:255.255.255.0 > inet6 addr: fe80::92e2:baff:fe61:e744/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:61670925 errors:0 dropped:0 overruns:0 frame:0 > TX packets:61670819 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3700268930 (3.7 GB) TX bytes:2590194254 (2.5 GB) > > > When pinging this ip address from an external host I > noticed internal_dev_recv() never gets called although I > see internal_dev_xmit() getting called. Not that its causing any functional > issue but I am wondering if this is the expected behavior. > > The call graph is attached. > > Thanks. >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
