Skip to content

wip tagged nat_apply - #333

Draft
nicolaskagami wants to merge 4 commits into
nsk/nat-3-natmapfrom
nsk/service-nat-entries
Draft

wip tagged nat_apply#333
nicolaskagami wants to merge 4 commits into
nsk/nat-3-natmapfrom
nsk/service-nat-entries

Conversation

@nicolaskagami

Copy link
Copy Markdown
Contributor

No description provided.

@nicolaskagami
nicolaskagami force-pushed the nsk/service-nat-entries branch from 7fa4258 to 267c875 Compare August 6, 2026 14:50
@nicolaskagami
nicolaskagami changed the base branch from main to nsk/nat-3-natmap August 6, 2026 14:51
@nicolaskagami
nicolaskagami force-pushed the nsk/service-nat-entries branch 2 times, most recently from ce210d2 to b19eeae Compare August 7, 2026 12:48
@nicolaskagami
nicolaskagami force-pushed the nsk/nat-3-natmap branch 2 times, most recently from 789c30c to 61774ca Compare August 7, 2026 13:47
@nicolaskagami
nicolaskagami force-pushed the nsk/service-nat-entries branch 2 times, most recently from 211e43e to 7f79bae Compare August 7, 2026 18:20
Tie each IP address family to its p4 table, match key, and action types
via a trait, with the table operations provided as default methods.
Replaces the duplicated per-family entry points.
Replace the duplicated v4/v6 mapping storage and logic with a single
NatEntry type and a NatMap generic over NatAddress; the public API keeps
its per-family signatures as thin wrappers.
@nicolaskagami
nicolaskagami force-pushed the nsk/service-nat-entries branch from 3f1f878 to 2734833 Compare August 13, 2026 23:36
@nicolaskagami
nicolaskagami force-pushed the nsk/nat-3-natmap branch 2 times, most recently from 1e580a3 to f415415 Compare August 14, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant