Hi,

Which version of Ryu are you using?

On my environment, length field can be get.

e.g.)
$ curl -X GET http://localhost:8080/stats/flow/1 | jq .
{
   "1": [
     {
       "duration_sec": 256,
       "byte_count": 0,
       "match": {
         "in_port": 1
       },
       "actions": [
         "OUTPUT:2"
       ],
       "idle_timeout": 0,
       "table_id": 0,
       "flags": 0,
       "cookie": 1,
       "hard_timeout": 0,
       "packet_count": 0,
       "length": 88,      # !!! the length of flow entry
       "priority": 11111,
       "duration_nsec": 423000000
     }
   ]
}

$ ryu-manager --version
ryu-manager 4.5

Thanks,
Iwase

On 2016年08月26日 10:00, Túlio Pascoal wrote:
> Hi,
>
> Can anyone help me in this thread? I really think it is an implementation
> problem in the REST API, Ryu or OpenFlow.
>
>
> Regards,
>
> --
> Túlio Albuquerque Pascoal
> <https://br.linkedin.com/pub/t%C3%BAlio-pascoal/a0/2a9/b69>
> <http://lattes.cnpq.br/3973060880564786>
>
> On 23 August 2016 at 15:55, Túlio Pascoal <tuliopasc...@gmail.com> wrote:
>
>> Hello folks,
>>
>> I would like to get the flow entries length, because I am needing this
>> information.
>>
>> I tried using ovs-ofctl from mininet but it did not work.
>>
>> So I saw that I could use the ryu REST api for it, by using curl -X GET
>> http://localhost:8080/stats/flow/1 where I was supposed to get the length
>> information of the flow, as you can see by the example in:
>> http://ryu.readthedocs.io/en/latest/app/ofctl_rest.html#
>> get-all-flows-stats
>>
>> However what I am getting from using it is:
>>
>> ryu@ryu-vm:~$ curl -X GET http://localhost:8080/stats/flow/1
>> {"1": [{"actions": ["SET_FIELD: {eth_dst:00:00:00:00:00:01}", "SET_FIELD:
>> {(Unknown field):192.168.1.200}", "SET_FIELD: {(Unknown
>> field):192.168.1.100}", "OUTPUT:1"], "idle_timeout": 100, "cookie": 0,
>> "packet_count": 7, "hard_timeout": 100, "byte_count": 581, "duration_nsec":
>> 445000000, "priority": 10, "duration_sec": 13, "table_id": 0, "match":
>> {"dl_type": 2048, "nw_proto": 6, "nw_src": "192.168.1.200", "in_port": 2,
>> "nw_dst": "192.168.1.100"}},
>> {"actions": ["SET_FIELD: {eth_dst:00:00:00:00:00:02}", "SET_FIELD:
>> {(Unknown field):192.168.1.100}", "SET_FIELD: {(Unknown
>> field):192.168.1.200}", "OUTPUT:2"], "idle_timeout": 100, "cookie": 0,
>> "packet_count": 5, "hard_timeout": 100, "byte_count": 12158,
>> "duration_nsec": 448000000, "priority": 10, "duration_sec": 12, "table_id":
>> 0, "match": {"dl_type": 2048, "nw_proto": 6, "nw_src": "192.168.1.100",
>> "in_port": 1, "nw_dst": "192.168.1.200"}},
>> {"actions": ["OUTPUT:4294967293"], "idle_timeout": 0, "cookie": 0,
>> "packet_count": 4, "hard_timeout": 0, "byte_count": 232, "duration_nsec":
>> 94000000, "priority": 0, "duration_sec": 312, "table_id": 0, "match": {}}]}
>>
>> As you can see no length field in any of the flows.
>>
>>
>>
>> Best regards,
>>
>> --
>> Túlio Albuquerque Pascoal
>> <https://br.linkedin.com/pub/t%C3%BAlio-pascoal/a0/2a9/b69>
>> <http://lattes.cnpq.br/3973060880564786>
>>
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Ryu-devel mailing list
> Ryu-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>

------------------------------------------------------------------------------
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Reply via email to