Changes between Version 4 and Version 5 of Internal/OpenFlow/Notes

Timestamp:

Jul 13, 2009, 10:38:35 PM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Notes

@@ -39 +39 @@
  * can a virtual switch be loaded with a default flow table that would allow it to function, at least until its table times out?
 
-=== SSL setup (7/13) ===
-using this site as reference: http://www.debian-administration.org/article/Creating_and_Using_a_self_signed__SSL_Certificates_in_debian
+=== SSL setup, things top know for the next day. (7/13) ===
+using this site as reference: http://www.debian-administration.org/article/Creating_and_Using_a_self_signed__SSL_Certificates_in_debian  
 
-except renaming the switch key and cert to what it would understand:
- *ca_cert.pem
- *sw_cert.pem
- *sw_key.pem
+except renaming the output .pem files to what it would understand:
+ *ca_cert.pem  - from cacert.pem
+ *sw_cert.pem   -  from cert.pem
+ *sw_key.pem   - from key.pem 
+
+for the Common Name, I just used the IP address of the CA, 192.168.203.75.  
 
 because in the example on the site ca_cert.pem is named cacert.pem, I had to change "cacert" to "ca_cert" in openssl.cnf for the very last part (signing the certificate):
@@ -53 +55 @@
 database = $dir/index.txt 
 new_certs_dir = $dir/newcerts 
-certificate = $dir/cacert.pem 
+certificate = $dir/ca_cert.pem       #change over here  
 private_key = $dir/private/cakey.pem 
 default_days = 365 
@@ -63 +65 @@
 policy = policy_match 
 }}}
-I am not sure if changing the name of the key from ofpswitch.key.pem to sw_key.pem after making/signing the certification will affect anything. will find out. 
+I am not sure if changing the name of the key from ofpswitch.key.pem to sw_key.pem after making/signing the certification will affect anything. 
+
+Some lessons for the day: [[BR]]
+ * the SD card will show up as /media/disk on the PC
+ * 
+
+things to do: 
+ * control VLAN on switch
+ * config control VLAN and statically assign PC to controller IP
+  * VLAN not used for any legacy networking purposes for controller
+ * packet sniff SSL handshake 
+
+==== VLAN 888 ====
+arbitrary VLAN for OFP controller, since nothing probably uses that high a VLAN number. Currently only gi 0/42 (formerly one of the trunk ports)
+{{{
+sw-sb09(config)# vlan 888
+!sw-sb09(config-vlan)# name "OpenFlow control VLAN"
+!sw-sb09(config-vlan)# interface gi 0/42
+!sw-sb09(config-if)# sh
+interface gigabitethernet 0/42
+  switchport mode trunk
+  switchport trunk allowed vlan 1,3,27-28
+  switchport trunk native vlan 1
+!
+!sw-sb09(config-if)# no sw mo tru
+!sw-sb09(config-if)# no switchport trunk allowed vlan 1,3,27-28
+!sw-sb09(config-if)# no switchport trunk nat vlan 1            
+!sw-sb09(config-if)# sh
+interface gigabitethernet 0/42
+  switchport mode access
+!
+!sw-sb09(config-if)# sw acc vlan 888
+!sw-sb09(config-if)# interface vlan 888
+!sw-sb09(config-if)# ip address 172.16.4.1 255.255.255.0
+!sw-sb09(config-if)# save                     
+sw-sb09(config-if)# 
+}}}
+this will probably not need a route specified for it since the controller is directly attached to the switch.    
  
+[[BR]]
+[[BR]]
+[[BR]]
+[[BR]]
+[wiki:Documentation/OpenFlow/ return to OpenFlow index]