Changes between Version 9 and Version 10 of Internal/OpenFlow/Notes

Timestamp:

Aug 4, 2009, 4:17:10 AM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Notes

@@ -193 +193 @@
 having issues with trying it, getting this error:
 {{{  
-A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using 
-a sendto call) no address was supplied. - getpeername(2) (Errno::ENOTCONN)
+A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram 
+socket using a sendto call) no address was supplied. - getpeername(2) (Errno::ENOTCONN)
 }}}
 
@@ -201 +201 @@
 idea for !OpenFlow: use code from reference model to simulate a handshake, display on a webpage or something else, to get a sense of how to integrate things 
 
-
-
+=== Anatomy of !OpenFlow Protocol (8/3) ===
+!OpenFlow Switch has a [http://www.openflowswitch.org/documents/openflow-spec-v0.9.0.pdf paper] you can read for information on how the protocol works. The initial handshake is the important piece of info that makes a switch communicate with what it considers a controller. 
+
+==== The Handshake ====
+The OFP handshake contains the following steps:
+
+ 1. OFPT_HELLO message - sent by both parties to negotiate what version of !OpenFlow to use 
+ 1. SSL connection (optional)
+ 1. OFPT_FEATURES_REQUEST - sent by controller
+ 1. OFPT_FEATURES_REPLY - returned by switch 
+ 1. ECHO reply/request or some flow actions 
+
+The steps need to be recreated, but there are several things that need to be done:
+ * when creating a socket in Ruby you need a port number, but it is a passive connection (ptcp) - the port can be anything
+ * pick apart either OF reference system or NOX for handshake code