Changes between Version 2 and Version 3 of GENIEducation/SampleAssignments/OpenFlowFirewallAssignment/onepage


Ignore:
Timestamp:
08/12/13 13:03:52 (6 years ago)
Author:
epittore@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIEducation/SampleAssignments/OpenFlowFirewallAssignment/onepage

    v2 v3  
    4646
    4747
     48This section contains a few tips that may help you out if you are using the Open vSwitch implementation provided with this tutorial.
     49
     50If you are using a hardware OpenFlow switch, your instructor can help you find equivalent commands.[[BR]]
     51
     52The Open vSwitch installation provided by the RSpec included in this tutorial is located in ''/opt/openvswitch-1.6.1-F15''. You will find Open vSwitch commands in ''/opt/openvswitch-1.6.1-F15/bin'' and ''/opt/openvswitch-1.6.1-F15/sbin''. If you add these paths to your shell’s ''$PATH'', you will be able to access their manual pages with man.
     53
     54'''Note that ''$PATH'' will not affect sudo, so you will still have to provide the absolute path to sudo; the absolute path is omitted from the following examples for clarity and formatting.'''
     55
     56 - '''2.1 ovs-vsctl'''[[BR]]
     57
     58 Open vSwitch switches are primarily configured using the ''ovs-vsctl'' command. You may find the ''ovs-vsctl show'' command useful, as it dumps the status of all virtual switches on the local Open vSwitch instance. Once you have some information on the local switch configurations, ''ovs-vsctl'' provides a broad range of capabilities to expand your network setup to more complex configurations for testing and verification. In particular, the subcommands ''add-br'', ''add-port'', and ''set-controller'' may be of interest.
     59
     60 - '''2.2 ovs-ofctl''' [[BR]]
     61
     62 The switch host configured by the given rspec listens for incoming OpenFlow connections on localhost port 6634.
     63 You can use this to query the switch state using the ''ovs-ofctl'' command. In particular, you may find the ''dump-tables'' and ''dump-flows'' subcommands useful. For example, {{{sudo ovs-ofctl dump-flows tcp:127.0.0.1:6634}}} will output lines that look like this:
     64 {{{
     65cookie=0x4, duration=6112.717s, table=0, n packets=1, n bytes=74, idle age=78,priority=5,tcp,
     66nw src=10.10.10.0/24 actions=CONTROLLER:65535
     67 }}}
     68
     69 This indicates that any TCP segment with source IP in the 10.10.10.0/24 subnet should be sent to the OpenFlow controller for processing, that it has been 78 seconds since such a segment was last seen, that one such segment has been seen so far, and the total number of bytes in packets matching this rule is 74.
     70
     71 - '''2.3 Unix utilities'''[[BR]]
     72
     73 The standard ping and ''/usr/sbin/arping'' tools are useful for debugging connectivity (but make sure your controller passes ''ICMP ECHO REQUEST'' and ''REPLY'' packets and ''ARP'' traffic, respectively!), and the command ''netstat -an'' will show all active network connections on a Unix host; the TCP connections of interest in this exercise will be at the top of the listing. The format of netstat output is out of the scope of this tutorial, but information is available online and in the manual pages.
     74
     75= Exercises =