Hi Jereme,
Hope I understood everything properly. I try to describe your testbed.
You should have a controller communicating with an instance of
OpenVSwitch. Then, there should be many hosts connected to this switch.
Each node should tag the traffic with a different VLAN id. Your problem
is that nodes can't communicate with the controller.
If what I wrote above is correct then this sounds normal. While the
switch communicates with the controller through a dedicated channel and
users hosts shouldn't see the controller.
Let's do an example:
controller
(10.0.0.1/30)
||
OVS IP to controller = 10.0.0.2/30
OVS
no ip on other ports
|| || || ||
H1 H2 H3 H4
Each host should have its own IP and VLAN, OVS can communicate on the
10.0.0.0/30 with the controller.
Hosts can communicate together just providing a kind of
intervaln-routing through OpenFlow (using the controller), but they'll
can never communicate with the controller directlly.
Let me know if I missed something, cheers,
Luca P.
Il 19/03/2013 16:13, Jereme Lamps ha scritto:
Hello!
I would like to set up a basic configuration with 1 openvswitch, 1
'control' node, and various other nodes. The control node needs to be
able to communicate with all of the other nodes, and all of the other
nodes need to be in separate vlans (not able to communicate with
eachother). I understand how to put the other nodes into separate
vlans, but I am then having trouble getting them to communicate with
my control node.
How would I configure the port the control node is on?
Thanks for your help,
Jereme
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
