Hi Folks, My question may be related to the discussion in this thread: http://openvswitch.org/pipermail/discuss/2011-September/005553.html
Until we upgraded to v1.2.2 we were unnecessarily setting in_port=OFPP_CONTROLLER in ofp_packet_out messages (with a single action ofp_action_output to a non-virtual port number). v1.2.2 these packets and its log shows a message like: Oct 31 06:41:46|03045|dpif|WARN|system@mido0: execute 1 failed (Invalid argument) on packet 66:48:9c:a3:8d:a4 > 52:54:00:12:34:56, ethertype ARP (0x0806), length 42: Reply 192.168.10.2 is-at 66:48:9c:a3:8d:a4, length 28 Setting in_port=OFPP_NONE fixes the problem. I just wanted to confirm my understanding of this behavior because the OpenFlow 1.0 spec seems to say that in_port is ignored unless the actions include an output to OFPP_TABLE: "If OFPP_TABLE is spec- ified as the output port of an action, the in_port in the packet_out message is used in the flow table lookup." Is OVS now enforcing that in_port=OFPP_NONE when OFPP_TABLE is not one of the output actions? thanks, Pino -- Pino de Candia Software Engineer, Midokura.com
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
