Hello,
We are facing a wrong behaviour of the ovs-OpenFlow switch within a network
entirely composed of virtual machines (based on Virtual Box).
Please find the related scheme below.
The tests configuration is as follows :
- 1 OF switch VM setup with OpenVswitch 1.1.1.
It is connected to both :
- an external bridge (through the physical interface Eth0)
- an internal bridge Net01 towards VM client1 (through eth1 virtual
interface)
- an internal bridge Net02 towards VM client 2 (through eth2 virtual
interface)
- 1 client1 VM connected to the OF switch VM (through the internal bridge Net01
and the virtual eth0 interface)
- 1 client2 VM connected to the OF switch VM (through the internal bridge Net02
and the virtual eth0 interface)
Configuration of the OF switch VM :
- installation of the openvswitch_mod.ko module
- creation of the dp0 datapath instance with 2 interfaces eth1 and eth2 (use of
ovs-dpctl)
- activation of the ovs-controller (for L2 MAC learning) : ovs-controller
ptcp:6633:127.0.0.1
- activation of the ovs-openflow : ovs-openflowd dp0 tcp:127.0.0.1:6633
-listen=ptcp:6634:127.0.0.1 -detach
- configuration of the flows/instruction (use of ovs-ofctl) :
ovs-ofctl add-flow tcp:127.0.0.1.6634 in_port=1,actions=output:2
ovs-ofctl add-flow tcp:127.0.0.1.6634 in_port=2,actions=output:1
Test procedure : ping from Client 2 to Client 1. Result : Host Unreachable. Client 1 has received Ethernet ARP Request frames broadcasted by Client 2. It sends Ethernet ARP Reply with its own mac address in turn. However the OF switch VM does not receive the reply frame. So : 1°) How to view the arp table and how to populate it at the OpenFlow switch ? 2°) What is wrong in our configuration ? Maybe specific options on ovs-controller and/or ovs-openflow are missing ? Best Regards, Corinne and Dina Hereafter the schema of our testbed
image001.emz
Description: image001.emz
oledata.mso
Description: oledata.mso
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
