On Wed, 23 May 2018 01:59:40 +0900, Soliman Awad Alshra´a Abdullah TU Ilmenau wrote: > > [1 <text/plain; iso-8859-1 (quoted-printable)>] > Hello all, > In my own Ryu application, the Controller doesn't receive any request from > the Switches immediately. > > Actually , I have 2 controllers and 4 switches. Each switch has 2 hosts > except switch 4. > the switches 1, 2 and 3 connected to Controller 1 and the switch 4 > connected to Controller 2. > > > C1 C2 > > / | \ | > > S1---S2 ---- S3 --------------------------- S4 > > / \ /\ /\ > > h1 h2 h3 h4 h5 h6 > > firstly, when the controllers handshake their switches. > C1 inserts a Table miss(S1,S2,S3) in order to send packets to S4. > C2 inserts a Table miss (S4) in order to send packets to C2. > > For example, when h1 pings h4, Switch S1 will send the inquiry to pass > through C2. After that, the enquiry goes to C1. > In the end, C1 sends a new entry table to S1 with higher priority to send the > new packets to C1 directly. > > My problem is when I try to let h1 to ping h4 again, I expect the packet goes > to C1 and I get ping from h4, but, The ping packet goes to C1, then return > to S2, then the packets goes to S3,S4 and C2 again. > > Can anyone explain me, why don't I get the ping ?
Does the ping succeed first time? > mininet@mininet-vm:~$ sudo ovs-ofctl dump-flows s1 > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=11.444s, table=0, n_packets=1, n_bytes=98, idle_age=11, > priority=100,in_port=1,dl_src=00:00:00:00:00:01 actions=CONTROLLER:65535 > cookie=0x0, duration=400.692s, table=0, n_packets=1, n_bytes=98, > idle_age=22, priority=1,in_port=1 actions=mod_vlan_vid:100,output:3 > cookie=0x0, duration=400.692s, table=0, n_packets=0, n_bytes=0, > idle_age=400, priority=1,in_port=2 actions=mod_vlan_vid:101,output:3 > > mininet@mininet-vm:~$ sudo ovs-ofctl dump-flows s2 > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=43.483s, table=0, n_packets=0, n_bytes=0, idle_age=54, > priority=100,in_port=3,dl_src=00:00:00:00:00:04 actions=CONTROLLER:65535 You are installing this high priority flow at ThreadingExample.foo. Your packet-in handler has code to add some flows but those flows will not take effect as they are low priority, IIUC. Checking increses in n_packets and n_bytes is a good way to know which flow entry is in effect. > cookie=0x0, duration=432.699s, table=0, n_packets=0, n_bytes=0, > idle_age=432, priority=1,in_port=2 actions=mod_vlan_vid:102,output:4 > cookie=0x0, duration=432.699s, table=0, n_packets=0, n_bytes=0, > idle_age=432, priority=1,in_port=3 actions=mod_vlan_vid:103,output:4 > cookie=0x0, duration=432.699s, table=0, n_packets=2, n_bytes=200, > idle_age=43, priority=1 actions=output:4 > I am still working to achieve what I mentioned previously. > I attached My initial script so, Please could you check it out. > > C1.py is the first ryu application. > To run it use the next line : > mininet@mininet-vm:~/ryu$ PYTHONPATH=. ./bin/ryu-manager --verbose > --ofp-listen- > host 127.0.0.1 > ryu/app/C1.py > > > C2.py is the second ryu application. > To run it use the next line : > mininet@mininet-vm:~/ryu$ PYTHONPATH=. ./bin/ryu-manager --verbose > --ofp-listen- > host 127.0.0.2 > ryu/app/C2.py > > custom1.py is the Topology > run it using : > mininet@mininet-vm:~$ sudo python custom1.py > > > my script code is just prepared to ping h1 to h4 Therefore, use (h1 ping -c1 > h4 ). > > Thanks a lot in advance > > Best regards > A.Soliman > [2 custom1.py <application/octet-stream (base64)>] > [3 C1.py <application/octet-stream (base64)>] > [4 C2.py <application/octet-stream (base64)>] > [5 <text/plain; us-ascii (7bit)>] > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > [6 <text/plain; us-ascii (7bit)>] > _______________________________________________ > Ryu-devel mailing list > Ryu-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ryu-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
