Changes between Version 13 and Version 14 of Internal/OpenFlow/SandBoxSetup

Timestamp:

Aug 10, 2009, 3:29:09 PM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/SandBoxSetup

@@ -221 +221 @@
 
 = Making use of NOX (8/6) = 
-Writing a controller by tying together the functional code defining !OpenFlow Protocol using Ruby turned out to be a pretty messy task. According to the NOX developers, it would be better to do some Python development on the NOX web-API to expose functionality that can be called using Ruby. 
+Writing a controller by tying together the functional code defining !OpenFlow Protocol using Ruby turned out to be a pretty messy task. According to the NOX developers, it would be better to do some Python development on the NOX web-API to expose functionality that can then be called using Ruby. 
 
 So enter NOX: http://noxrepo.org
 
-Install with git: [[BR]]
-apt-get install git-core   [[BR]] 
-git clone git://noxrepo.org/noxcore   [[BR]]
-
+(Borrowing heavily from the noxrepo instructions:  http://noxrepo.org/manual/installation.html setup) Install with git: 
+{{{
+apt-get install git-core   # if you don't have git installed
+git clone git://noxrepo.org/noxcore
+cd noxcore/
+./boot.sh
+mkdir build/
+cd build/
+../configure --with-python=yes
+make
+make check 
+}}}
 
 === Installing NOX on the Console ===
-We tried to use git, but that didn't work due to firewall issues. It did work on the PC, so the package was tarred and scp-d to SB9. 
-
-For it to build properly, the following had to be installed.
+Simply following the above installation steps caused the Console to yell at us about things not being installed. For it to build properly, the following had to be installed:
  * libtool
  * libboost1.35-dev
@@ -281 +287 @@
 
 
-the switch will recognize a controller with the command 
-
-`./nox_core -i ptcp:6633 `
-
-./nox_core -h will give you all the commands available. 
+nox_core is found under noxcore/build/src/. [[BR]] 
+./nox_core -h will give you all the commands available. The switch will recognize a controller with the command 
+{{{
+./nox_core -i ptcp:6633 
+}}}
+NOX also includes, among other things, a python-based L2 switch, which can be run like this:
+{{{
+./nox_core -v -i ptcp:6633 pyswitch
+}}}
+The timeout for the flows are about 22 seconds, very quick compared to the OF reference system.
+{{{
+sw-sb09> showflow detail
+--------------------------------------------------------------------------------
+Matching key
+  Input port  : 26                    VLAN ID     : 65535(0xffff)
+  MAC SA      : 00:0f:ea:83:a0:5c     MAC DA      : 00:0f:ea:84:9b:30
+  TYPE        : 0x800[IP]             IP protocol : 1[ICMP]
+  IP SA       : 192.168.1.2/32        IP DA       : 192.168.1.1/32
+  Source port : 8(0x8)                Dest port   : 0(0)
+Information
+  Idle timeout: 5 sec                 Hard timeout: 0 sec
+  Priority    : 65535
+  IFP slice no: 15                    IFP entry no: 1
+  Packet count: 17                    Byte count  : 98
+  Created     : Sat Feb 26 22:56:23 2000
+  Expires     : Sat Feb 26 22:56:45 2000
+  Action type : 0[OUTPUT]             Max length  : 0
+                                      Output port : 25(0x19)
+--------------------------------------------------------------------------------
+}}}
+
+