Changes between Version 26 and Version 27 of Internal/OpenFlow/Notes

Timestamp:

Oct 30, 2009, 2:54:30 PM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Notes

@@ -1 +1 @@
 = Notes =
 This section covers discussions and some background work that went into this project. 
-
-== Overview ==
-The things covered here are:
- 
- * DHCP relay agents 
- * VLANS
- * Trunking 
 
   
@@ -337 +330 @@
 === 9/15 ===
 
- * ca - quiz on friday (non-sequitor)
- * meeting at 2 - try to get out of work. 
  * group acl on switches : ok 
  * update perl-Net libraries on centOS
@@ -358 +349 @@
  * Reinstall NetFPGA !OpenFlow software
  * Move NetFPGA to new chassis
- * CA Ch2
- * probability/ DSPD  
-
+ 
 == NetFPGA lives! 10/17 ==
 The box that was set up by Nithin finally works -  it passed the OpenFlow switch regression test.
@@ -366 +355 @@
 The other box has a compromised NIC - the network does not work if the machine is started up while connected to the LAN, however it functions if it is connected after start-up. The on-board NIC is incompatible with drivers that come with CentOS 5.2; as a standby solution, another NIC has been slapped on for the net-install, after which I will try to update the drivers.  
 
+== L2TP SUCCESS!!!! 10/29 ==
+
+The setup process was actually not so pain full. We only needed 2 packages ''vtun'' and ''bridge-utils''. We copied the config files almost verbatim from (http://omf.mytestbed.net/wiki/omf/L2HowTo). The only exception being we changed the client address to  10.40.0.251. 
+
+Log messages on both machines seem to indicate success. We'll have to "test" it with some switching sauce. To bring up the br0 interface we need to use ifup (not ifconfig dev up). Note this will fail if ''bridge-utils'' is not installed since the interface is virtual and made by brctl.  Once br0 is up, restarting vtun caused many messages to appear in the syslog of landing1 (where our packets go to die). 
+
+== CentOS shinanigans, Ubuntu NetFPGA compatibility. ==
+CentOS proved to ba a difficult beast to deal with when it came to getting it to work with anything. Notably speaking:
+ * CentOS 5.2 realtek NIC driver incompatibility (will give you a great time trying to do the net-install)
+ * NetFPGA drivers do not compile without kernel update (what it uses expects the use of a different kernel version due to dependencies)
+ * Even after the FPGA is working, kernel modules for !OpenFlow switches failing to build properly
+
+Supposedly, NetFPGAs are capable of working with machines running Ubuntu. hopefully this works.
+ 
+ * Ubuntu-NetFPGA Compatibility info: http://www.netfpga.org/netfpgawiki/index.php/Ubuntu_Compatibility#NetFPGA_Beta_Changes_.28for_Ubuntu.29
+
+---So, the other box is now running Ubuntu 8.04 desktop edition. 
+They seem to have changed a few things around, i.e. run is run.pl, ect. You also need an account to download the NetFPGA base package.  
 
 [[BR]]
@@ -373 +380 @@
 [wiki:Internal/OpenFlow/ return to OpenFlow index]
 
-== L2TP SUCCESS!!!! ==
-
-The setup process was actually not so pain full. We only needed 2 packages ''vtun'' and ''bridge-utils''. We copied the config files almost verbatim from (http://omf.mytestbed.net/wiki/omf/L2HowTo). The only exception being we changed the client address to  10.40.0.251. 
-
-Log messages on both machines seem to indicate success. We'll have to "test" it with some switching sauce. To bring up the br0 interface we need to use ifup (not ifconfig dev up). Note this will fail if ''bridge-utils'' is not installed since the interface is virtual and made by brctl.  Once br0 is up, restarting vtun caused many messages to appear in the syslog of landing1 (where our packets go to die).