[ovs-discuss] Group actions incorrectly set vni

[Ben Pfaff]

On Mon, Aug 29, 2016 at 04:57:51PM +0800, Wilence Yao wrote:
> Hi all,
> 
> In the environment, I have add the flow as this :
> 
> ```
>  cookie=0x0, duration=12.336s, table=0, n_packets=9, n_bytes=378,
> reset_counts priority=100,in_port=5
> actions=set_field:0x64->tun_id,resubmit(,1)
>  cookie=0x0, duration=78.315s, table=1, n_packets=40, n_bytes=1680,
> priority=100,tun_id=0x64 actions=group:1
> ```
> 
> and a group:
> 
> ```
> group_id=1,type=select,bucket=actions=output:3,bucket=actions=output:4
> ```
> 
> Then I sent packet use ofport 5 (tap1),  it will match above flows.
> What expected is encapsulate as vxlan and vni=0x64, output to ofport 3 or
> ofport 4 (select).
> 
> But, Indeed it output to ofport 3 but vni=0.
> I sniffed in the physical interface use tcpdump, which confirmed that vni=0
> ```
> 13:55:00.981475 00:0c:29:cb:b2:2f > 00:0c:29:48:17:b8, ethertype IPv4
> (0x0800), length 92: 192.168.178.129.60563 > 192.168.178.131.4789: VXLAN,
> flags [I] (0x08), vni 0
> fa:16:3e:25:fd:77 > Broadcast, ethertype ARP (0x0806), length 42: Request
> who-has 1.1.1.1 tell 1.1.1.100, length 28
> 
> ```
> 
> The kernel flow is:
> 
> ```
> #ovs-dpctl dump-flows ovs-system
> recirc_id(0),in_port(3),eth(src=fa:16:3e:25:fd:77,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),
> packets:4653, bytes:195426, used:0.235s,
> actions:set(tunnel(dst=192.168.178.131,ttl=64,flags(df))),2
> ```
> 
> Does anyone konw why does it happed?
> 
> 
> More Information:
> 
> Environment:
> ```
> # ovs-vsctl show
> cce09669-adf1-445c-ba70-2cc53dae1c6c
>     Bridge "br1"
>         Port "vxlan1"
>             Interface "vxlan1"
>                 type: vxlan
>                 options: {remote_ip="192.168.178.130"}
>         Port "br1"
>             Interface "br1"
>                 type: internal
>         Port "vxlan2"
>             Interface "vxlan2"
>                 type: vxlan
>                 options: {remote_ip="192.168.178.131"}
>         Port "tap1"
>             tag: 1
>             Interface "tap1"
>                 type: internal
>     ovs_version: "2.5.0"

If you want the tunnel key to come from the flow, you need to specify
key=flow in the interface configuration.