Jesse, Can i do the following:
I create an OVS bridge with only 2 VXLAN tunnels. So, i have two virtual ports in my bridge. I have eth0, over which i physically recieve the VXLAN packets, and i dont add that to OVS. Is this configuration possible? I thought that i ought to add eth0 also to my bridge. Thanks, Abhishek On Wed, Jul 29, 2015 at 6:14 AM, Abhishek Verma <abhishekv.ve...@gmail.com> wrote: > So youre saying that in DPDK + OVS, OVS actually retains a copy of the > entire routing and ARP tables. Interesting, i hadnt realized that. > > About eth0, my assumption was that a port over which a packet needs to be > sent out or received on MUST always be added to the OVS bridge. How can i > trap a packet arriving on eth0, if it has not been added to the OVS bridge? > > Thanks, Abhishek > > On Wed, Jul 29, 2015 at 6:09 AM, Jesse Gross <je...@nicira.com> wrote: > >> The DPDK path operates differently - the kernel stack in not invoked. >> In that case, eth0 does need to be attached to OVS but, again, not in >> the same bridge. OVS will sync the routing table from the kernel but >> otherwise implements ARP, etc. internally and retains control of the >> packet until it is sent out on the physical interface. >> >> On Tue, Jul 28, 2015 at 5:02 PM, Abhishek Verma >> <abhishekv.ve...@gmail.com> wrote: >> > Thanks Jesse. >> > >> > How does this work when OVS is running in the user space along with >> DPDK. >> > Does OVS again send packets to Linux stack for forwarding? I thought the >> > whole point there was NOT to involve the Linux stack. >> > >> > Asking this since i thought that since eth0 is a part of the OVS >> bridge, its >> > OVS that actually frames the entire packet and sends it out. >> > >> > Thanks, Abhishek >> > >> >> >> >> It does not make sense to have eth0 in the same bridge as the VXLAN >> >> port since they are not in the same network segment (encapsulated vs. >> >> not). OVS simply sends tunneled packets as IP to the Linux stack, >> >> similar to any other application. These packets do not re-enter OVS >> >> unless there is another bridge that is in the normal Linux forwarding >> >> path. >> > >> > >> > >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
