[ovs-discuss] No packet-in with ofp_action_output + OFPP_CONTROLLER

[Ben Pfaff]

On Wed, Feb 16, 2011 at 05:31:48PM -0800, kk yap wrote:
> I am OVS kernel datapath with ovs-openflowd.  I have installed the
> following flow entries.
> 
>  cookie=0x0, duration=292.116s, table_id=0, n_packets=0, n_bytes=0,
> priority=24576,icmp actions=CONTROLLER:1500
>  cookie=0x0, duration=292.116s, table_id=0, n_packets=189,
> n_bytes=36725, priority=24576,udp actions=CONTROLLER:1500
>  cookie=0x0, duration=292.116s, table_id=0, n_packets=0, n_bytes=0,
> priority=24576,tcp actions=CONTROLLER:1500
>  cookie=0x0, duration=292.155s, table_id=0, n_packets=897,
> n_bytes=53820, priority=0 actions=drop
> 
> I see that the second entry (i.e., match on UDP packet with dl_type
> and ip_proto set) is incrementing the counters for n_packets and
> n_bytes.  But there is no packet-ins received by the controller!  This
> is with OVS (at head of master branch).

This is quite odd.  I started a controller like this:

ovs-controller --pidfile --max-idle=5 ptcp: --with-flows=flows -vvconn

with the following in the 'flow' file:

priority=20000,ip,nw_dst=192.168.0.1,actions=controller,normal
priority=0,actions=normal

and then ran a "ping" from 192.168.0.1 to 192.168.0.2.  I saw many
messages like this in the ovs-controller output:

Feb 17 09:42:15|00122|vconn|DBG|tcp:192.168.0.20:39099: received: OFPT_PACKET_IN (xid=0x0): total_len=98 in_port=1 (via action) data_len=98 (unbuffered)
tunnel0:in_port0001:tci(0) mac50:54:00:00:00:07->50:54:00:00:00:05 type0800 proto1 tos0 ip192.168.0.2->192.168.0.1

So the problem is not obvious to me.