Hi, Ben: Thanks very much, the information really helps. What I am confused is about GRE tunnel http://blog.scottlowe.org/2013/05/07/using-gre-tunnels-with-open-vswitch/ In the above blog, each host uses two bridges, one for GRE, one for physical port but there seems no patch port between 2 bridges. I searched google, all said that in this condition it will use routing to connect 2 bridges I have tried to setup an environment following the blog, but failed to communicate the 2 VMs That's why I eager to know how to communicate 2 ports in different bridge.
At 2014-09-29 07:53:01, "Ben Pfaff" <b...@nicira.com> wrote: >On Sun, Sep 28, 2014 at 01:45:51PM +0800, ychen wrote: >> I am confused about the usage of multi bridge in openvswitch. >> 1. under which environment will we use multi bridge? >> 2. how can 2 ports in different bridge communicate? exp: > >Q: How do I connect two bridges? > >A: First, why do you want to do this? Two connected bridges are not > much different from a single bridge, so you might as well just have > a single bridge with all your ports on it. > > If you still want to connect two bridges, you can use a pair of > patch ports. The following example creates bridges br0 and br1, > adds eth0 and tap0 to br0, adds tap1 to br1, and then connects br0 > and br1 with a pair of patch ports. > > ovs-vsctl add-br br0 > ovs-vsctl add-port br0 eth0 > ovs-vsctl add-port br0 tap0 > ovs-vsctl add-br br1 > ovs-vsctl add-port br1 tap1 > ovs-vsctl \ > -- add-port br0 patch0 \ > -- set interface patch0 type=patch options:peer=patch1 \ > -- add-port br1 patch1 \ > -- set interface patch1 type=patch options:peer=patch0 > > Bridges connected with patch ports are much like a single bridge. > For instance, if the example above also added eth1 to br1, and both > eth0 and eth1 happened to be connected to the same next-hop switch, > then you could loop your network just as you would if you added > eth0 and eth1 to the same bridge (see the "Configuration Problems" > section below for more information). > > If you are using Open vSwitch 1.9 or an earlier version, then you > need to be using the kernel module bundled with Open vSwitch rather > than the one that is integrated into Linux 3.3 and later, because > Open vSwitch 1.9 and earlier versions need kernel support for patch > ports. This also means that in Open vSwitch 1.9 and earlier, patch > ports will not work with the userspace datapath, only with the > kernel module.
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
