[ovs-discuss] Connecting two open vswitches on different hosts
trojan.of.troy at gmail.com
Fri Jul 15 04:41:48 UTC 2011
This doesn't seem to work with an IPIP tunnel created using the "ip tunnel
This is what I did on both machines:
ip tunnel add net1 mode ipip remote <remote_addr> local <local_addr> ttl 255
ifconfig net1 192.168.255.12/24 up # on machine 1
ifconfig net1 192.168.255.13/24 up # on machine 2
I was able to ping machine1 from machine2 and ssh into either machine.
ifconfig net1 0.0.0.0 up
ovs-vsctl add-port br0 net1
ifconfig br0 192.168.255.12/24 up # on machine 1
After doing this, route -n showed
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.255.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
After this, I wasn't able to ping the machines any more.
Am I going wrong somewhere? Thanks.
On Tue, Jul 12, 2011 at 11:49 PM, Justin Pettit <jpettit at nicira.com> wrote:
> On Jul 12, 2011, at 11:34 PM, Nicholas Bastin wrote:
> > On Wed, Jul 13, 2011 at 02:31, Aniruddha Laud <trojan.of.troy at gmail.com>
> >> I am following the cookbook at http://openvswitch.org/?page_id=146 . I
> >> want to create one single bridge, but I want to be able to have open
> >> vswitches running on different hosts and still be able to talk to each
> >> other. In short, I want to remove the eth0 - eth0 connection mentioned
> >> the cookbook and replace it with a tunnel if possible, so that a VM on
> >> can communicate with a VM on host2.
> > It probably depends on the type of tunnel, but I don't see any problem
> > with this. Ben or Justin might have more input on what kinds of
> > interfaces you can use, but I would think that if you create any
> > tunnel that creates an interface, you're ok - just add that interface
> > to the bridge (instead of, or in addition to, eth0).
> Sounds about right to me. OVS supports a couple different tunnel types,
> but here's a command to attach a GRE tunnel to a bridge:
> ovs-vsctl add-port br0 gre0 -- set interface gre0 type=gre
> The physical interface (e.g., eth0) doesn't need to be attached to the
> bridge, since the host's IP stack will be used.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss