A motivation of this change is a better modularity.
I.e. Make packet lib independent from ofproto.
Signed-off-by: YAMAMOTO Takashi
---
ryu/lib/packet/arp.py | 2 +-
ryu/lib/packet/ether_types.py | 27 +++
ryu/lib/packet/ethernet.py| 2 +-
ryu/lib/packet/in_p
A motivation of this change is a better modularity.
I.e. Make packet lib independent from ofproto.
Signed-off-by: YAMAMOTO Takashi
---
ryu/lib/pack_utils.py | 32 +++
ryu/lib/packet/bgp.py | 2 +-
ryu/ofproto/nx_actions.py
Hi,
Thank you for your patch.
As you say, EXT-208 was included in Openflow v1.3.1,
but Openflow v1.2 dose not include this change.
So, I wonder if ofproto_v1_2.py need to be fixed like OF1.3+ ...
Thanks
On 2015年02月12日 09:05, Shu Shen wrote:
> Invalid error code OFPQCFC_EPERM should be OFPSCFC_E
Hi,
> I get a message in return of a request, but the msg.xid is not in
> self.waiters, but I supposed that it would be there because
> "send_stats_request" of ryu/lib/ofctl_V1_0.py
> do it,
ofctl_v1_0.py set the dpid and xid to waiters.
https://github.com/osrg/ryu/blob/master/ryu/lib/ofctl_v1
Hi,
On 2015年02月11日 01:52, Clément Rault wrote:
> Hi,
>
> Do you if it's possible to mix the fast failover and the select group
> type functionalities?
>
> For example I would like to have a group which forward the packet to 3
> outports (each having the same weight) but only to the outports wher
Hi,
On 2015年02月11日 02:03, Clément Rault wrote:
> Hi,
>
> In the documentation it's written "SET_FIELD Set a “field” using
> “value” (The set of keywords available for “field” is the same as
> match field)"
>
> so basically I could use a set-field on any of these fields.
>
> But when I look at t
Invalid error code OFPQCFC_EPERM should be OFPSCFC_EPERM instead. This
is EXT-208 that was included in Openflow v1.3.1
Signed-off-by: Shu Shen
---
ryu/ofproto/ofproto_v1_2.py| 2 +-
ryu/ofproto/ofproto_v1_3.py| 2 +-
ryu/ofproto/ofproto_v1_4.py| 2
Hello, Dear Ryu Developers
I want to know does the latest ryu with gui
https://github.com/yamada-h/ryu/tree/gui-patch-v3-rebase
support openflow 1.3 now?
or if there is any latest version that does?
Best Regard.
--
Dive i
Hi FUJITA:
I'm using heavily customized ofagent which is totally different from
the origin one.
My agent calls remove flow inside packet_in handler which causes deadlock.
the packet_in handler is blocked by remove flow waiting for the
barrier reply, but the receive queue is flooded with packet_i