On 2/26/13 2:20 AM, Arnaud M wrote:
So an openflow device has to be the initiator of the connection ? And it shouldn't listen on any port ?
Yes.
If I want to manage my openvswitch only with proactive flow, the easy would be to initiate a connection (from my "controller"), to push some flow then to disconnect. But to do that, the switch has to listen on a specific port (to be the server)
OpenFlow does not normally work that way. (Although this may change in OF 1.4.) However, OVS has a nonstandard extension that allows it to listen for connections; see ovs-vsctl set-controlller ... ptcp:... in http://openvswitch.org/cgi-bin/ovsman.cgi?page=utilities%2Fovs-vsctl.8
But when I read spec, I don't think it's the right way... It's better to let the switch initiate the connection that has to be maintain and then use this permanent channel to push my flow when i need.
Right. The controller should not close an OpenFlow connection because the switch will just reopen it again.
-- Wes Felter IBM Research - Austin _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
