Hi Clément,
On 2015年02月27日 21:12, Clément Rault wrote:
> Hi,
>
> Thanks for your answer.
>
> Yes I get the same error message (that's why I mean by syntax error,
> sorry if it wasn't clear...).
>
> And I'm almost sure that it comes from this line:
> {"type": "POP_VLAN" }
> but I'm surprised because it's what is written in the documentation
> (http://ryu.readthedocs.org/en/latest/app/ofctl_rest.html#description-of-actions-on-request-messages):
> POP_VLAN Pop the outer VLAN tag {“type”: “POP_VLAN”}
>
> I'm not sure what you meant with "required fields are missing in
> match" but I tried with
> {
> "type": "POP_VLAN",
> "field": "vlan_vid"
> }
> and it didn't work.
For "required fields are missing in match",
I meant the following command.
curl -X POST -d '{
"dpid": 2,
...,
...,
"match":{
"vlan_vid": 1 # <--- "required fields in match"
},
"actions":[
{
"type": "POP_VLAN"
},
{
"type": "OUTPUT",
"port": 1
}
]
}' http://localhost:8080/stats/flowentry/add
>
> So my question is:
> How can I remove the vlan tag? What should I change or add to {“type”:
> “POP_VLAN”} in the action bucket?
>
> Best,
> Clément
>
> On 27 February 2015 at 03:34, Yusuke Iwase <[email protected]> wrote:
>> Hi Clément,
>>
>> I got the following error message with "--verbose" option.
>>
>> $ sudo ryu-manager --verbose ryu.app.ofctl_rest
>> ...
>> 127.0.0.1 - - [27/Feb/2015 11:17:21] "POST /stats/flowentry/add HTTP/1.1"
>> 200 115 0.000875
>> error msg ev version: 0x4 msg_type 0x1 xid 0x60dc17cb
>> OFPErrorMsg(code=10,data='\x04\x0e\x00h`\xdc\x17\xcb\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00+g\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\x00\x01\x00\x00\x00\x01\x00\x12\x80\x00\n\x02\x08\x00\x80\x00\x18\x04\x0b\x00',type=2)
>> type 0x2 code 0xa 0x4 0xe 0x0 0x68 0x60 0xdc 0x17 0xcb 0x0 0x0 0x0 0x0 0x0
>> 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x2b
>> 0x67 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x0 0x1 0x0
>> 0x0 0x0 0x1 0x0 0x12 0x80 0x0 0xa 0x2 0x8 0x0 0x80 0x0 0x18 0x4 0xb 0x0
>> ...
>>
>> Error message shows OFPErrorMsg(code=10,...,type=2).
>> ===
>> In OpenFlow Spe1.3.4
>> ===
>> ofp_error_type:
>> OFPET_BAD_ACTION = 2, /* Error in action description. */
>> ===
>> ofp_bad_action_code:
>> OFPBAC_MATCH_INCONSISTENT = 10, /* Action can’t apply for this match,
>> or Set-Field missing prerequisite. */
>> ===
>>
>> I think required fields are missing in match.
>> e.g.) "dl_vlan" or "vlan_vid"
>>
>> Thanks
>>
>> On 2015年02月27日 01:09, Clément Rault wrote:
>>> (sorry for the multiple emails)
>>>
>>> Now I understood what was missing with the vlan.
>>>
>>> And I tried to add an action that will remove the vlan tag so that the
>>> host can answer to the icmp request.
>>>
>>> But I'm getting a syntax error even though I am using what's written
>>> in the documentation (here
>>> http://ryu.readthedocs.org/en/latest/app/ofctl_rest.html#description-of-actions-on-request-messages).
>>>
>>> curl -X POST -d '{
>>> "dpid": 2,
>>> "cookie": 1,
>>> "cookie_mask": 1,
>>> "table_id": 0,
>>> "idle_timeout": 0,
>>> "hard_timeout": 0,
>>> "priority": 11111,
>>> "flags": 1,
>>> "match":{
>>> "nw_dst": "11.0.0.2",
>>> "eth_type": 2048
>>> },
>>> "actions":[
>>> {
>>> "type": "POP_VLAN"
>>> },
>>> {
>>> "type": "OUTPUT",
>>> "port": 1
>>> }
>>> ]
>>> }' http://localhost:8080/stats/flowentry/add
>>>
>>> What should I change?
>>>
>>> Best,
>>> Clément
>>>
>>> On 26 February 2015 at 10:35, Clément Rault <[email protected]> wrote:
>>>> I started wireshark after starting mininet and now I see the different
>>>> interfaces (including s1-eth3). Sorry for my mistake!
>>>>
>>>> Best,
>>>> Clément
>>>>
>>>> On 26 February 2015 at 10:25, Clément Rault <[email protected]>
>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Thanks for your answer!
>>>>>
>>>>> On 26 February 2015 at 07:21, Yusuke Iwase <[email protected]>
>>>>> wrote:
>>>>>>
>>>>>> Hi Clément,
>>>>>>
>>>>>> I don't think the above command is wrong.
>>>>>>
>>>>>> $ curl -X GET http://localhost:8080/stats/groupdesc/1
>>>>>> {
>>>>>> "1": [
>>>>>> {
>>>>>> "type": "SELECT",
>>>>>> "group_id": 1,
>>>>>> "buckets": [
>>>>>> {
>>>>>> "watch_port": 2,
>>>>>> "weight": 1000,
>>>>>> "watch_group": 4294967295,
>>>>>> "actions": [
>>>>>> "OUTPUT:2"
>>>>>> ]
>>>>>> },
>>>>>> {
>>>>>> "watch_port": 3,
>>>>>> "weight": 1,
>>>>>> "watch_group": 4294967295,
>>>>>> "actions": [
>>>>>> "PUSH_VLAN:33024",
>>>>>> "SET_FIELD: {vlan_vid:4097}",
>>>>>> "OUTPUT:3"
>>>>>> ]
>>>>>> }
>>>>>> ]
>>>>>> }
>>>>>> ]
>>>>>> }
>>>>>>
>>>>>> How about capturing the output packets at port 3?
>>>>>> I captured packets at port 3, VLAN-tagged packets were output.
>>>>>> (Please see attached png file.)
>>>>>
>>>>>
>>>>> I tried to do that but didn't manage to only capture these packets (I
>>>>> don't see s1-eth3 in the list of the interfaces where I can capture
>>>>> packets
>>>>> in Wireshark). What filter do you apply to do that in Wireshark?
>>>>>
>>>>>>
>>>>>> By the way, did you assign VLAN ID to Host 3 (which is connected to port
>>>>>> 3 of switch)?
>>>>>> If not, I think Host 3 cannot reply for VLAN-tagged packets.
>>>>>
>>>>>
>>>>> I'm not sure to understand what you mean by "assign VLAN ID to Host 3".
>>>>> Can you please elaborate?
>>>>>
>>>>> To port 3 I have a switch connected (and a rule which forwards the packet
>>>>> depending on the IP destination address and not on the VLAN id so it
>>>>> should
>>>>> always work).
>>>>>
>>>>> I attached a file with my rules.
>>>>>
>>>>> Best,
>>>>> Clément
>>>>>
>>>>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel
