[Ryu-devel] Flow not added with ipv4 match field

Hi, I am trying to match packet only based on source IPv4 address Using Internal calls, no flow is added and no error OFPError message actions = [parser.OFPActionSetQueue(2)] inst = [parser.OFPInstructionActions(ofproto.OFPIT_APPLY_ACTIONS, actions),

Re: [Ryu-devel] Problem with simple switch 13 app in multiple switch topology

Hi, This problem seems to be caused by the loop in your Topology1. simple_switch_13 is just a sample application for the getting started, and this App does not aware of the looped topology. To detect or solve the loop in your topology, I guess you need to implement your own App. FYI,

[Ryu-devel] [PATCH 7/7] packet/bgp: Fix subtype for Traffic Filtering Actions of Flow Specification

This patch sets the constant value so that you can omit argument "subtype" for Traffic Filtering Action of Flow Specification. Signed-off-by: Shinpei Muraoka --- ryu/lib/packet/bgp.py | 44 1 file changed, 40 insertions(+),

[Ryu-devel] [PATCH 0/7] Implement user interface of Flow Specification

The following patches add the user interface of Flow Specification. Also, add the Route Distinguisher to data structure for VPNv4 Flow Specification. Shinpei Muraoka (7): packet/bgp: Implement user interface of Flow Specification test_bgp: Add test cases for user interface of Flow

[Ryu-devel] [PATCH 4/7] packet/bgp: Fix data structure for VPNv4 Flow Specification

The Route Distinguisher did not include in data structure for VPNv4 Flow Specification. This patch adds the Route Distinguisher to data structure for VPNv4 Flow Specification. For details, refer to Chapter 8 of RFC 5575. Signed-off-by: Shinpei Muraoka ---

[Ryu-devel] [PATCH 6/7] packet/bgp: Unify variable names for Flow Specification

Currently, FLOW_SPEC and FLOWSPEC constants are mixed, so this patch will unify to FLOWSPEC. Signed-off-by: Shinpei Muraoka --- ryu/lib/packet/bgp.py | 20 ++-- ryu/lib/packet/safi.py | 4 ++-- 2 files changed, 12 insertions(+), 12 deletions(-) diff

[Ryu-devel] [PATCH 5/7] packet/bgp: Add the address converter for Flow Specification

Argument "addr" of "_FlowSpecPrefixBase" must be specified in the network address. If argument "addr" specified in the host address, this patch converts the given address into the network address. Signed-off-by: Shinpei Muraoka --- ryu/lib/packet/bgp.py | 3 ++- 1

[Ryu-devel] [PATCH 2/7] test_bgp: Add test cases for user interface of Flow Specification

Signed-off-by: Shinpei Muraoka --- ryu/tests/unit/packet/test_bgp.py | 133 ++ 1 file changed, 133 insertions(+) diff --git a/ryu/tests/unit/packet/test_bgp.py b/ryu/tests/unit/packet/test_bgp.py index 07b21f9..dec1dae 100644 ---

[Ryu-devel] [PATCH 3/7] library_packet_ref:Add bgp reference for Flow Specification

Signed-off-by: Shinpei Muraoka --- doc/source/library_packet_ref.rst | 4 1 file changed, 4 insertions(+) diff --git a/doc/source/library_packet_ref.rst b/doc/source/library_packet_ref.rst index 2e8ee1a..85b6071 100644 --- a/doc/source/library_packet_ref.rst +++

Re: [Ryu-devel] Flow not added with ipv4 match field

Hi, If you want to match packets, you must satisfy the prerequisites. For example, if you want to match packet based on source IPv4 address, you must specify "eth_type" as the prerequisite (in OpenFlow V1.0, "dl_type"). In the OpenFlow Spec, you can see the prerequisites for each match

Re: [Ryu-devel] Flow not added with ipv4 match field

I was trying to add dl_type as match field, it was giving error that's why I was not adding it. Now its working Thanks -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!

[Ryu-devel] [PATCH 1/7] packet/bgp: Implement user interface of Flow Specification

Signed-off-by: Shinpei Muraoka --- ryu/lib/packet/bgp.py | 247 +- 1 file changed, 244 insertions(+), 3 deletions(-) diff --git a/ryu/lib/packet/bgp.py b/ryu/lib/packet/bgp.py index cfe8cff..47feeb3 100644 ---