Changes between Version 7 and Version 8 of GENIExperimenter/Tutorials/NFV/Ryu/HandlingIntrusionwithRyu

Timestamp:

05/18/17 12:39:17 (7 years ago)

Author:

matta@cs.bu.edu

Comment:

--

GENIExperimenter/Tutorials/NFV/Ryu/HandlingIntrusionwithRyu

@@ -67 +67 @@
 3. Type something on the s1 window and you should see it on the destination window.
 
-4. In another separate window for s1,  we will create attack traffic, which in our case are ICMP messages. To send ICMP messages to destination, run the following ping command: 
+4. In another separate window for s1,  we will generate attack traffic, which in our case are ICMP messages. To send ICMP messages to the destination, run the following ping command: 
 
    - ''' ping destination'''
 
-The first few ping messages are able to reach destination since it takes some time for the controller to get the intrusion detection results from VNFs via the RINA distributed application, but after a few seconds, all following messages will not be able to reach destination, and you can see the following output: 
+The first few ping messages are able to reach destination since it takes some time for the controller to get the intrusion detection results from the VNFs via the RINA distributed application, but after a few seconds, all following ping messages will not be able to reach the destination, and you should see the following output: 
 
 {{{
@@ -78 +78 @@
  }}}
 
-5. Type something on the s1 window for netcat and you should NOT see it on the destination window. If you go to the controller window which runs the Ryu controller, you can see it drops all traffic from the attacker with the following output:
+5. Type something on the s1 window for netcat and you should NOT see it on the destination window. If you go to the controller window which runs the Ryu controller, you can see that all traffic from the attacker is dropped with the following output:
 
 {{{