https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-655 netvirt <p>New netvirt classifier is intercepting packets meant for a SF on egress. The problem is on table 221, where supposedly any packet that has not just being classified should return to the egress dispatcher:</p> <p>New netvirt classifier not setting tun id to 0 when egressing to SFF</p> <p> cookie=0xf005ba1100000003, duration=1214.452s, table=221, n_packets=256, n_bytes=28672, priority=260,nsh_mdtype=1 actions=goto_table:222<br/> cookie=0xf005ba1100000003, duration=1214.452s, table=221, n_packets=1, n_bytes=42, priority=250 actions=resubmit(,220)</p> <p>nsh_mdtype=1 is being used as a flag of recently classified packet but it is not an appropiate one, as packets being handled by SFF logic will also have that set.</p> <p>An alternate option is to set a magic value into CX on the ACL flow, like 0xFFFFFFFF. This will flag a just-classified packet, and reset it afterwards.</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-655

New netvirt classifier handling already classified packets on egress

Bug Resolved Done Jaime Caamaño Ruiz Jaime Caamaño Ruiz Fri, 5 May 2017 15:47:19 +0000 Fri, 19 May 2017 05:05:35 +0000 Fri, 19 May 2017 05:05:35 +0000 Carbon General 0 4 <p>Please ignore "New netvirt classifier not setting tun id to 0 when egressing to SFF" on the above comment as that was pasted by mistake.</p> <p>One first proposal is to set C1 to 0xFFFFFF on the ACL flow. Then on beguinning of egress pipeline, if C1 does not have that value we assumed thats a packet bound for the SF and already classified so it is resubmitteed to dispatcher. Otherwise, C1 is reset to 0 and handling continues:</p> <p>cookie=0xf005ba1100000002, duration=3129.696s, table=101, n_packets=0, n_bytes=0, priority=500,tcp,in_port=1,nw_src=10.0.0.0/24,tp_dst=80 actions=push_nsh,load:0x1-&gt;NXM_NX_NSH_MDTYPE[],load:0x3-&gt;NXM_NX_NSH_NP[],load:0x13-&gt;NXM_NX_NSP<span class="error">&#91;0..23&#93;</span>,load:0xff-&gt;NXM_NX_NSI[],load:0xffffff-&gt;NXM_NX_NSH_C1[],load:0-&gt;NXM_NX_NSH_C2[],load:0xac130002-&gt;NXM_NX_REG0[],resubmit(,17)</p> <p>...</p> <p>cookie=0xf005ba1100000003, duration=3157.512s, table=221, n_packets=0, n_bytes=0, priority=260,nshc1=16777215 actions=load:0-&gt;NXM_NX_NSH_C1[],goto_table:222</p> <p>Patches submitted for carbon <span class="error">&#91;1&#93;</span> and Nitrogen <span class="error">&#91;2&#93;</span>.</p> <p><span class="error">&#91;1&#93;</span> <a href="https://git.opendaylight.org/gerrit/#/c/56667/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/56667/</a><br/> <span class="error">&#91;2&#93;</span> <a href="https://git.opendaylight.org/gerrit/#/c/56610/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/56610/</a></p> <p>We are looking to build Carbon RC2 tomorrow 5/18 at 23:59 UTC time assuming there are no blocker bugs. Is there an ETA for when a fix can be merged and this bug resolved for stable/carbon branch?</p> <p>(In reply to A H from comment #4)<br/> &gt; We are looking to build Carbon RC2 tomorrow 5/18 at 23:59 UTC time assuming<br/> &gt; there are no blocker bugs. Is there an ETA for when a fix can be merged and<br/> &gt; this bug resolved for stable/carbon branch?</p> <p>The patches are ready and listed in the previous comment</p> <p>earlier carbon patch noted was abandoned. this carbon patch is here:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/56610/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/56610/</a></p> Development External issue ID 8388 External issue URL Rank 0|i01t53: