When it doesn't work I have a host unreachable while trying to ping a device on the 192.168.200.x. I see that the icmp packets are routed to the right interface (the one attached to the bridge with the tunnel, with the IP=192.168.200.4), but it seems that the tunnel is too long to see its end:
root@bm-1:~# ping 192.168.200.1 PING 192.168.200.1 (192.168.200.1) 56(84) bytes of data. >From 192.168.200.4 icmp_seq=2 Destination Host Unreachable >From 192.168.200.4 icmp_seq=3 Destination Host Unreachable >From 192.168.200.4 icmp_seq=4 Destination Host Unreachable >From 192.168.200.4 icmp_seq=5 Destination Host Unreachable >From 192.168.200.4 icmp_seq=6 Destination Host Unreachable >From 192.168.200.4 icmp_seq=7 Destination Host Unreachable JC On Nov 2, 2011, at 10:16 AM, Jesse Gross wrote: > On Wed, Nov 2, 2011 at 10:09 AM, JC Martin <[email protected]> wrote: >> gre1 was built with the following command: >> [root@xcp-2 ~]# ovs-vsctl add-port xapi1 gre1 -- set interface gre1 >> type=gre options:remote_ip=172.16.188.200 >> >> I tried to replicate the xenserver setup on bm-1 by adding a bridge with >> eth0 as a port, adding another bridge with the tunnel and an interface, but >> it has not been successful (i tried also with only one bridge with the >> tunnel and an interface). Ideally, on bm-1 I would like to have two >> interfaces, one on 172.16.188.x and one on my private network (192.168.200.x) > > That should be fine as long as bm-1 is reachable on 172.16.188.200. > What do you see when it doesn't work? _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
