Hi everyone, After reading the openflow spec 1.0.0, I'v found this :
*The switch must be able to establish communication with a controller at a user-configurable (but otherwise fixed) IP address, using a user-specified port. If the switch knows the IP address of the controller, the switch initiates a standard TLS or TCP connection to the controller. Traffic to and from the OpenFlow channel is not run through the OpenFlow pipeline. Therefore, the switch must identify incoming traffic as local before checking it against the flow tables. Future versions of the protocol specification will describe a dynamic controller discovery protocol in which the IP address and port for communicating with the controller is determined at runtime. So an openflow device has to be the initiator of the connection ? And it shouldn't listen on any port ? 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) 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. Am I right ? Thanks for response, Arnaud M *
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
