[Ryu-devel] Bug REST Ryu Delete all flow entry

2017-08-02 Thread Nicholas Brasini
Hi guys! In my web-app with REST call Ryu, I have found a possible bug. When I launch url -X DELETE http://localhost:8080/stats/flowentry/clear/1 to delete every flow in switch 1, the OUTPUT:CONTROLLER (flow of controller Ryu) deleted with OUTPUT:1 and OUTPUT:2. But if I launch h1 ping h2 in t

Re: [Ryu-devel] multi-controllers

2017-08-02 Thread Iwase Yusuke
Hi Vichhaiy, Ryu does not provide the standard way for such purpose. I guess there are too many ways to implement clusters. The following is the discussion about the similar subject and it might be some help if you are intend to implement clustering features. https://www.mail-archive.com/ryu-d

Re: [Ryu-devel] Fields 'OUTPUT' and 'in_port' REST Ryu

2017-08-02 Thread Fujimoto Satoshi
Hi, Nicholas Do you mean that you would like to get source/dest mac from the packet "via REST API" ? If so, ryu.app.ofctl_rest does not provide such a feature. In general terms, you can get source/dest mac of the packet by receiving Packet-In from switches. Packet-In contains a ethernet frame

Re: [Ryu-devel] Bug REST Ryu Delete all flow entry

2017-08-02 Thread Fujimoto Satoshi
Hi, Nicholas I think you may use simple_switch_xx.py for OpenFlow < 1.3. In OpenFlow < 1.3, the packet which is not matched to any flows will be sent as Packet-In (OUTPUT:CONTROLLER). It may be that the controller installs OUTPUT:1 and OUTPUT:2 in Packet-In handler. In any case, I would like