Thanks William. Does your statement mean, by network design, vxlan tunnel ports and underlay bridge ports should not be part of a single bridge domain?
-Vasu *Vasu Dasari* On Wed, May 6, 2020 at 3:44 PM William Tu <[email protected]> wrote: > On Sun, May 03, 2020 at 11:12:04PM -0400, Vasu Dasari wrote: > > Hi, > > > > I am trying a userspace vxlan test case scenario as follows. ap0, fp0, > ap1 > > and fp1 are namespaces where in packets from ap0 are sent to fp0 over > vxlan > > tunnel and packets from ap1 to fp1 are sent over second vxlan tunnel. And > > br0 for the bridge is handling ARP, route, etc. Note that br0 has two > > addresses on assigned to it. > > > > On executing the script with following command: > > sudo make -s -C _build-gcc/ check-system-userspace TESTSUITEFLAGS='-k > > "modified ping over vxlan tunnel"' > > > > I see that OVS times out and leaving behind br0 and ovs-netdev > interfaces. > > But, if I comment out the one of the addresses on br0 at least the script > > will be successful but the ping on second tunnel will not be successful. > > > > My question is: > > 1. Is this use case supported in userspace OVS mode? > > 2. Am I missing something in configuration? > > > > Thanks > > -Vasu > > > > > > +------+ > > +---+ | | +---+ > > |ap0+------+ +------+fp0| > > +---+ | | +---+ > > | ovs | > > +---+ | br0 | +---+ > > |ap1+------+ +------+fp1| > > +---+ | | +---+ > > +------+ > > > > > > > > We usually have an underlay bridage and overlay bridge. > And the vxlan device is attached to the overlay, and the > underlay bridge has the outer ip assigned. > William > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
