Rare project developers

[mc36 <>]

hi,
thanks for playing with it and finding a workaround...
that field is not exactly ternary, it was just written this way to shrink 
that table...
so the values are very well defined and could be listed explicitly... imho 
i'll do that,
i'll validate on the test cases and then we can replace ternary to exact for 
that field...
br,
cs



On 6/2/22 10:27, Alexander Gall wrote:
> Interesting. The problem goes away when I add a redundant entry with a
> fixed value of mpls_encap_decap_sap_type in the global part of
> include/ig_ctl_pkt_pre_emit.p4:
>
> diff --git a/p4src/include/ig_ctl_pkt_pre_emit.p4
> b/p4src/include/ig_ctl_pkt_pre_emit.p4
> index c53597f..0575f34 100644
> --- a/p4src/include/ig_ctl_pkt_pre_emit.p4
> +++ b/p4src/include/ig_ctl_pkt_pre_emit.p4
> @@ -309,6 +309,7 @@ ig_md.nexthop_id:
>               (1, 0, 0, 0, 0, 0, 0, 0, 4, _):act_pkt_srv_l3vpn_ipv4_encap();
>               (1, 0, 0, 0, 0, 0, 0, 0, 6, _):act_pkt_srv_l3vpn_ipv6_encap();
>   #endif
> +            (0, 0, 0, 0, 0, 0, 0, 0, 4, CPU_PORT):act_pkt_send_to_cpu();
>               (0, 0, 0, 0, 0, 0, 0, 0, _, CPU_PORT):act_pkt_send_to_cpu();
>               (0, 0, 0, 0, 0, 0, 0, 1, _, CPU_PORT):act_pkt_send_to_cpu();
>               (0, 0, 0, 0, 0, 0, 1, 0, _, CPU_PORT):act_pkt_send_to_cpu();
>
> That seems like an easy workaround :)