783
edits
Specialization Software-defined Networking (Winter 2014/2015): Difference between revisions
Jump to navigation
Jump to search
Specialization Software-defined Networking (Winter 2014/2015) (view source)
Revision as of 07:33, 27 March 2015
, 27 March 2015→27 March
| Line 113: | Line 113: | ||
* Exercise IX: Debugging | * Exercise IX: Debugging | ||
** We have done kinetic firewall in exercise VII and imitated the same firewall using pox in exercise VIII. Now, we will imitate the same firewall using pyretic. | ** We have done kinetic firewall in exercise VII and imitated the same firewall using pox in exercise VIII. Now, we will imitate the same firewall using pyretic. | ||
** The solution is provided here [], test if it is able to block h1 when "infected" | |||
*** start controller | ** The solution is provided here [], test if it is able to block h1 when "infected". Note that we will only use the "infected == True" for this exercise. | ||
*** start mininet: | *** start controller (in /home/mininet/pyretic folder): pyretic.py pyretic.examples.gardenwall_internetcode | ||
*** start mininet: sudo mn --controller=remote --topo=single,3 --mac --arp | |||
*** check h1 ping h2 | *** check h1 ping h2 | ||
*** Now infect h1: | *** Now infect h1: python json_sender.py -n infected -l True --flow="{srcmac=00:00:00:00:00:01}" -a 127.0.0.1 -p 50001 | ||
*** check h1 ping h2. We should be able to observe that this traffic is blocked. | |||
** Now, we move on to the debugging part | |||
*** check h2 ping h3, what happens? | |||
*** Now, modify the given code to allow h2 traffic to pass through to h3 | |||
== Group Discussion Papers == | == Group Discussion Papers == | ||