Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ovsp4rt] Prepare[V6]TunnelTermTableEntry adds undefined match key field #617

Open
ffoulkes opened this issue Aug 10, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@ffoulkes
Copy link
Contributor

The ES2K variant of the PrepareTunnelTermTableEntry() function adds a match field for the Bridge ID (user_meta.pmeta.bridge_id).

  match->set_field_id(GetMatchFieldId(p4info, IPV4_TUNNEL_TERM_TABLE,
                                      IPV4_TUNNEL_TERM_TABLE_KEY_BRIDGE_ID));
  match->mutable_exact()->set_value(EncodeByteValue(1, tunnel_info.bridge_id));

The Linux Networking P4 program does not define this match field for ipv4_tunnel_term_table.

As a result, the TableEntry contains a match_field with an ID of -1 (maxint when rendered as an unsigned integer).

  {
   "field_id": 4294967295,
   "exact": {
    "value": "Vg=="
   }
  },

PrepareV6TunnelTermTableEntry() has the same problem.

@ffoulkes ffoulkes added the bug Something isn't working label Aug 10, 2024
@ffoulkes ffoulkes changed the title [ovsp4rt] PrepareTunnelTermTableEntry adds undefined match key field [ovsp4rt] Prepare[V6]TunnelTermTableEntry adds undefined match key field Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant