On Mon, Apr 11, 2011 at 10:13 PM, benzwt benzwt <ben...@gmail.com> wrote: > Thank for you guys reply so quickly. After I receive your suggestion. > > I try to bind ip on br0 (or should i create a internal interface vifn > on br0 then bind ip on vif0??) > > ifconfig br0 192.168.200.5 on host2 > ifconfig br0 192.168.100.5 on host1 > but found that I can't ping these ip from other side!! > then create gre interface > ovs-vsctl add-port br0 gre0 -- set interface gre0 type=gre > options:remote_ip=192.168.200.5 on host1 > ovs-vsctl add-port br0 gre0 -- set interface gre0 type=gre > options:remote_ip=192.168.100.5 on host2
Fundamentally the problem you have is with the topology of your bridges. The interface that you expect the GRE packets to egress on (i.e. the one that would be found via a routing table lookup of the remote_ip) cannot be in the same bridge as the GRE port, as that will lead to a loop. Normally you would have a bridge with a GRE port and one or more virtual interfaces (br0 is in this category, as it effectively the virtual interface for the local machine). These interfaces would have IP addresses that correspond to traffic inside the tunnel and is independent from remote_ip (though if you give br0 an IP, it should not overlap with the physical network as it will confuse the routing table). eth0 should have an IP that can be used to communicate to remote_ip but should not be in a bridge at all or at the very least not in the same bridge as the GRE port. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
