Hi, Alex, Thank you for the reply,
I spent the whole weekend to solve it I create br0 for every server, and make the first server as the gateway then disable all physical NICs and attach eth0 of everyone to their own br0s; then set all br0s in the same subnet every VM can communicate and access internet now (because I attach the first server to internet, and its IP is just in the subset where the VMs are in) Best, -- Nan On Monday, 21 October, 2013 at 11:03 AM, Alex Wang wrote: > sorry for this delayed reply, > > there is one thing I noticed below: > > On Sat, Oct 19, 2013 at 8:23 AM, Nan <codingcat...@gmail.com > (mailto:codingcat...@gmail.com)> wrote: > > Hi, Alex, > > > > I tried your suggestion, it seems that the problem is still there > > > > In host 1: I have the tunnel ready > > > > zhunan@zhunan-PowerEdge-R210-II:~$ sudo ovs-vsctl show > > [sudo] password for zhunan: > > 01db97ba-8174-40f6-9648-f8f14a317e2b > > Bridge "br0" > > > > Port "tunnel_to_host1" > > Interface "tunnel_to_host1" > > type: gre > > options: {remote_ip="192.168.2.2"} > > Port "br0" > > Interface "br0" > > type: internal > > > > > > > > > > Here you did not add any physical interface (eth0 or eth1). > > > > and the routing table looks like > > > > zhunan@zhunan-PowerEdge-R210-II:~$ route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use > > Iface > > default 192.168.55.1 0.0.0.0 UG 100 0 0 br0 > > link-local * 255.255.0.0 U 1000 0 0 br0 > > 192.168.2.0 * 255.255.255.0 U 1 0 0 eth1 > > > > > > where 192.168.55.1 is the gateway to access internet > > > > the devices are : > > > > br0 Link encap:Ethernet HWaddr d4:ae:52:c7:cf:08 > > inet addr:192.168.55.142 Bcast:192.168.55.255 Mask:255.255.255.0 > > inet6 addr: fe80::d6ae:52ff:fec7:cf08/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > RX packets:12580 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:5038 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:3489191 (3.4 MB) TX bytes:587503 (587.5 KB) > > > > > > > > But here, the br0 is assigned with eth0's original ip and mac address. > > It seems to me that you just did > "ovs-vsctl del-port eth0" > "ovs-vsctl del-port eth1" > But you didn't reset the address. > With your configuration, you should reset the br0's address to 0. > Or you should try creating the br0 and configure it again. > > Another useful command for debugging is the "ovs-appctl dpif/dump-flows > [bridge_name]" command > It prints out good info about kernel flows (how the kernel will handle the > packet) >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
