On Tue, Oct 22, 2013 at 11:22 PM, Sukyoung Oh <[email protected]> wrote: > I appreciate for your answer. thank you for your attention. > > As I mentioned before, I am trying to use the openvswitch on DomU domain. (I > am using Xen) > > specifically, my intent is to control the flows that come into DomU from > VFs(SR-IOV) using openvswitch. > > In my experiment, my guest(DomU), there is three interfaces. One is > vif(eth0) connected to Dom0 and the others are VFs(eth1, eth2) connected to > each node directly. > > ovs was installed. and I did following instruction. > > ovs-vsctl add-br br0; > ovs-vsctl add-port br0 eth0. > ovs-vsctl add-port br0 eth1. > ovs-vsctl add-port br0 eth2. > > as a result, ovs-vsctl show, > > Bridge "br0" > port "eth2" > Interface "eth2" > port "br0" > Interface "br0" > type : internal > port "eth1" > Interface "eth1" > port "eth0" > Interface "eth0" > > In my case, eth1(VF)'s IP address is configured 10.0.2.2 and connected to a > node 10.0.2.1 > eth2(VF)'s IP address is configured 10.0.1.2 and connected > to a node 10.0.1.1 > > and linux kernel route table is like following > Destination Gateway Genmask Flags Metric Ref UseIface > 163.152.162.0 * 255.255.255.0 U 0 0 > br0 > 10.0.1.0 * 255.255.255.0 U 0 0 > br0 > 10.0.2.0 * 255.255.255.0 U 0 0 > br0 > > I tried to ping each node. > > ping 163.152.162.xx is worked well > But > ping 10.0.1.1 or ping 10.0.2.1 is not worked.
It doesn't make sense to use OVS and Linux routing in this combination. You shouldn't have IP addresses directly on the interfaces of the OVS bridge and since routing is relying on this behavior it won't work properly. It's actually not clear why you need OVS at all in this situation. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
