Re: [Ryu-devel] Ryu behaviour

2019-03-09 Thread Diarmuid O Briain
Maen, Thanks for all your help, whatever hair I had left is well gone now ;-) anyway I conclude that the Netgear switch has a terrible OpenFlow implementation. I got another server with 2 ethernet cards (8 ports) and installed OvS on it, connected it up and it all worked fine. I still cannot find

Re: [Ryu-devel] Ryu behaviour

2019-02-17 Thread Diarmuid O Briain
Iwamoto, Thanks. Does the Ryu team do any bakeoff type work with OpenFlow hardware vendors ? Has any been done with Netgear? Do you know why there is a differen e between the simple_switch_13.py that comes in the python3-ryu package and that which Maen pointed to on the git repository? Regards,

Re: [Ryu-devel] Ryu behaviour

2019-02-17 Thread IWAMOTO Toshihiro
I checked your PDF document. Packet counts of the table-miss flow entry is strange in the hardware switch setup. Maybe the controller isn't getting expected packet-ins, which can be the reason why the forwarding flow entries aren't populated. I have no idea if this is due to hardware problems or co

Re: [Ryu-devel] Ryu behaviour

2019-02-16 Thread Maen Artimy
Yes. OVS becomes a standard switch when you disable openflow. There may be other things going on. A fresh start may be a good idea. Maen On Sat, Feb 16, 2019 at 4:18 PM Diarmuid O Briain wrote: > Maen, > > The irony is that when I disable OpenFlow on the switch it immediately > starts switching

Re: [Ryu-devel] Ryu behaviour

2019-02-16 Thread Diarmuid O Briain
Maen, The irony is that when I disable OpenFlow on the switch it immediately starts switching ;-) I guess Fail-Over is working at least. (OF-SW) (Config)# *no openflow enable * 199.9.9.11_Host# *ping 199.9.9.22* Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 199.9.9.22, timeou

Re: [Ryu-devel] Ryu behaviour

2019-02-16 Thread Maen Artimy
No I didn't see the question. I'm assuming you are talking about this FlowManager: https://github.com/martimy/flowmanager. The two apps may conflict if they are using the same port (8080), otherwise try. ryu-manager ~/flowmanager/flowmanager.py ryu.app.ofctl_rest BTW, you asked What is the origin

Re: [Ryu-devel] Ryu behaviour

2019-02-16 Thread Diarmuid O Briain
Maen, I understand. Why I wonder is the version with the python3-ryu package as it is? Is that the Ryu group or Ubuntu repository package management? BTW did you see the question I asked about Flow Manager not working with the REST API. Is that normal or can the two be ran together ? Regards, D

Re: [Ryu-devel] Ryu behaviour

2019-02-16 Thread Diarmuid O Briain
Maen, Interesting, I compared the *simple_switch13.py* file you linked me to and the one that comes with the *python3-ryu* package (installed with apt-get install python3-ryu). $ *diff /usr/lib/python3/dist-packages/ryu/app/simple_switch_13.py maen_version_simple_switch_13.py* 105c105 <

Re: [Ryu-devel] Ryu behaviour

2019-02-16 Thread Maen Artimy
Diarmuid, There is something odd about the application you are running. The simple_switch_13.py should match three fields not two. Also it should not output the packet to the same input port (see line 105) . So I would start by checking if the application is correct. https://github.com/osrg/ryu/blo