[ovs-discuss] Problem with set tunnel id action in ovs

[Tomer Pearl]

Hello OVS community,

I'm using Opendaylight controller and trying to set an action in a flow that will set the tun_id field of packets that are going through a VxLAN tunnel.

I'm receiving the following error in the ovs-vswitchd.log file:

2014-10-20T13:30:37.636Z|00875|ofp_actions|WARN|bad action at offset 0 (OFPBAC_BAD_SET_TYPE):
00000000 00 19 00 18 80 00 4d 10-00 00 00 00 00 00 00 05
00000010 7f ff ff ff ff ff ff ff-00 00 00 10 00 00 00 04
00000020 ff ff 00 00 00 00 00 00-
2014-10-20T13:30:37.636Z|00876|connmgr|INFO|West1<->tcp:192.168.231.18:6653: sending OFPBAC_BAD_SET_TYPE error reply to OFPT_FLOW_MOD message

I'm attaching a Wireshark screen capture of the flow_mod I'm sending.

Thanks,
Tomer.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/discuss/attachments/20141020/d7fdc3b9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovs-tunnel-id-pcap.png
Type: image/png
Size: 110134 bytes
Desc: ovs-tunnel-id-pcap.png
URL: <Loading Image...>

[Ben Pfaff]

Post by Tomer Pearl
Hello OVS community,
I'm using Opendaylight controller and trying to set an action in a flow that will set the tun_id field of packets that are going through a VxLAN tunnel.
00000000 00 19 00 18 80 00 4d 10-00 00 00 00 00 00 00 05
00000010 7f ff ff ff ff ff ff ff-00 00 00 10 00 00 00 04
00000020 ff ff 00 00 00 00 00 00-
2014-10-20T13:30:37.636Z|00876|connmgr|INFO|West1<->tcp:192.168.231.18:6653: sending OFPBAC_BAD_SET_TYPE error reply to OFPT_FLOW_MOD message
I'm attaching a Wireshark screen capture of the flow_mod I'm sending.

I found and fixed one bug while investigating this. It wasn't
directly related to what you're reporting (and won't have any effect
on it) but I gave you credit in the commit message anyhow because your
email led me to find it.

The issue is that your set_field includes a mask. No released
OpenFlow version allows masks in set_field actions. However, the
OpenFlow 1.5 draft specification does, and OVS has some support for
OF1.5 that includes that feature, so if you want to use masked
set_fields, you can upgrade to a bleeding-edge OVS and use OpenFlow 1.5.
If you do it that way, then OVS interprets your actions as:
actions=set_field:0x5/0x7fffffffffffffff->tun_id,output:4