On Wed, 25 Jun 2014 21:28:00 -0700
Srini Seetharaman wrote:
> Hi all:
> Attached is a simple patch that solves an exception that I faced when the
> get_desc_stats() call was made even before some switch descriptions were
> archived. Hope you can accept it.
>
> Thanks
> Srini.
Looks good to me.
Hi all:
I noticed a problem with topology discovery when used in combination
with the simple_switch_13. It may be best for the packet_in handler of
simple_switch to ignore LLDP packets.
I made a patch like the one attached for myself. I'm submitting it in
case you find it reasonable to push upstre
Hi all:
Attached is a simple patch that solves an exception that I faced when the
get_desc_stats() call was made even before some switch descriptions were
archived. Hope you can accept it.
Thanks
Srini.
0001-Initializing-the-variable-s-so-that-the-get_desc_sta.patch
Description: Binary data
On Wed, 25 Jun 2014 14:59:45 +0800
Jason Huang wrote:
> Hi All,
>
> There are two flows in our flow table of an OF switch:
>
> flow #1 : match{ in_port: 2} action{[output:3]}
> flow #2 : match{ in_port: 2, src_mac:11:22:33:44:55:66} action{[output:4]}
>
> when I use REST API of Ryu 3.9 to delet
Dear All,
I am currently working on a project to implement multicast using SDN. As
part of the module I am required to identify the immediate neighbours of a
switch.
Following is the code sample which I have written. The sample shall return
all the links irrespective of the switch.
Can
I don't want to write a directive of sphinx in scripts, but
I was not able to find other methods.
Signed-off-by: Yoshihiro Kaneko
---
doc/source/ryu_app_api.rst | 6 +
ryu/lib/packet/bgp.py | 2 +
ryu/lib/packet/vlan.py | 2 +
ryu/lib/stringify.py
Hello, thanks for taking my needs into account! My (few) responses inline:
On 23 June 2014 04:38, FUJITA Tomonori
wrote:
> Hi,
>
> On Thu, 19 Jun 2014 18:00:34 +0200
> Jaume Devesa wrote:
>
> > my name is Jaume Devesa from Midokura. I have presented a *spec * for
> > OpenStack Juno to create
Hi All,
There are two flows in our flow table of an OF switch:
flow #1 : match{ in_port: 2} action{[output:3]}
flow #2 : match{ in_port: 2, src_mac:11:22:33:44:55:66} action{[output:4]}
when I use REST API of Ryu 3.9 to delete flow #1 by using following rest
api of ofctl_rest.py:
http://{contro
