It's "not yet". I'd like to implement them, but I'm not sure how to do it because connection-tracking state, for any given connection, is embedded in the kernel of some hypervisor, which may not be one that ovn-trace is running on (if ovn-trace is even running on a hypervisor).
One option would be to supply connection-tracking metadata on the ovn-trace command line, e.g. something like --ct=est,rel or --ct=new. Then ct_next could simply set ct_state to the specified values. This would allow testing given scenarios. Would that help your use case? On Tue, Nov 29, 2016 at 10:41:12PM +0000, Michael Kashin wrote: > OK, had a look at the source code of ovn-trace and it looks like ,indeed, > none of the conntrack actions are implemented yet. > Should it read as "not yet" or "will not" be implemented? > > On 28 Nov 2016 9:28 p.m., "Michael Kashin" <[email protected]> wrote: > > > Hi All, > > I'm having issues running ovn-trace for anything other than L2 flow. I > > have OVN+Neutron and a small topology with 3 VMs working fine (both nb and > > sb DBs are populated). whenever i do a trace for a L2 flow (only specify > > inport, eth.src and eth.dst) I see the expected result. Whenever I do a L3 > > flow trace I always get the following error: > > > > [root@controller-1 ~]# ovn-trace ed728b49-d632-4bdb-a65c-804311a3fea4 > > 'inport=="26c23a54-6a91-48fd-a019-3bd8a7e118de" && eth.src == > > fa:16:3e:4f:2f:b8 && eth.dst == fa:16:3e:0d:df:ea && ip4.src == 10.0.0.2 && > > ip4.dst == 20.0.0.1 && ip.ttl == 32' > > 2016-11-28T21:21:49Z|00001|ovntrace|WARN|reg0[3] = put_dhcp_opts(offerip > > = 20.0.0.9, netmask = 255.255.255.0, router = 20.0.0.1, mtu = 1442, > > server_id = 20.0.0.1, lease_time = 43200); next;: parsing actions failed > > (Syntax error at `offerip' expecting DHCPv4 option name.) > > 2016-11-28T21:21:49Z|00002|ovntrace|WARN|reg0[3] = put_dhcp_opts(offerip > > = 10.0.0.5, netmask = 255.255.255.0, router = 10.0.0.1, mtu = 1442, > > server_id = 10.0.0.1, lease_time = 43200); next;: parsing actions failed > > (Syntax error at `offerip' expecting DHCPv4 option name.) > > 2016-11-28T21:21:49Z|00003|ovntrace|WARN|reg0[3] = put_dhcp_opts(offerip > > = 10.0.0.2, netmask = 255.255.255.0, router = 10.0.0.1, mtu = 1442, > > server_id = 10.0.0.1, lease_time = 43200); next;: parsing actions failed > > (Syntax error at `offerip' expecting DHCPv4 option name.) > > # ip,reg14=0x2,vlan_tci=0x0000,dl_src=fa:16:3e:4f:2f:b8,dl_ > > dst=fa:16:3e:0d:df:ea,nw_src=10.0.0.2,nw_dst=20.0.0.1,nw_ > > proto=0,nw_tos=0,nw_ecn=0,nw_ttl=32 > > > > ingress(dp="neutron-7ee25b49-7803-497b-b8d2-7f0ed0106e29", > > inport="26c23a54-6a91-48fd-a019-3bd8a7e118de") > > ------------------------------------------------------------ > > --------------------------------------------- > > 0. ls_in_port_sec_l2 (ovn-northd.c:2827): inport == > > "26c23a54-6a91-48fd-a019-3bd8a7e118de" && eth.src == {fa:16:3e:4f:2f:b8}, > > priority 50 > > next(1); > > 1. ls_in_port_sec_ip (ovn-northd.c:1974): inport == > > "26c23a54-6a91-48fd-a019-3bd8a7e118de" && eth.src == fa:16:3e:4f:2f:b8 && > > ip4.src == {10.0.0.2}, priority 90 > > next(2); > > 3. ls_in_pre_acl (ovn-northd.c:2245): ip, priority 100 > > reg0[0] = 1; > > next(4); > > 5. ls_in_pre_stateful (ovn-northd.c:2363): reg0[0] == 1, priority 100 > > ct_next; > > *** ct_* actions not implemented > > > > Apologies if it's something stupid but I don't see it. > > > > > _______________________________________________ > discuss mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
