Skip to content

Conversation

@qmonnet
Copy link
Member

@qmonnet qmonnet commented Jan 16, 2026

Work in progress.

This needs to be rebased on top of #1198, once it is merged.

Currently, this PR also misses:

  • New tests to validate the behaviour of the changes in flow-filter
  • Equivalent changes in NAT context tables to handle the "default" destinations properly

@qmonnet qmonnet added this to the GW R2 milestone Jan 16, 2026
@qmonnet qmonnet requested a review from Fredi-raspall January 16, 2026 22:11
@qmonnet qmonnet self-assigned this Jan 16, 2026
@qmonnet qmonnet added the area/nat Related to Network Address Translation (NAT) label Jan 16, 2026
Base automatically changed from pr/qmonnet/default-vpc to main January 16, 2026 23:00
@qmonnet qmonnet force-pushed the pr/qmonnet/handle-default branch from 21032d1 to f5d2633 Compare January 16, 2026 23:59
Because the follow-up commits should be based on the changes from
#1198, but we just need
this tiny change to get the rest to compile.
This method will be used in a follow-up commit.

Signed-off-by: Quentin Monnet <qmo@qmon.net>
Make sure that we account for "default" VpcExpose when we retrieve the
destination VPC discriminant for the packet.

Internally, we don't add a prefix for the default destination into the
tables, because we'd have to handle overlap to some extent. Instead, we
add a per-source-VPC value to use as a fallback when no other
destination prefix match.

At the moment, the code assumes that each VPC accepts at most one
"default" destination.

Signed-off-by: Quentin Monnet <qmo@qmon.net>
@qmonnet qmonnet force-pushed the pr/qmonnet/handle-default branch from f5d2633 to 5053ce2 Compare January 17, 2026 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/nat Related to Network Address Translation (NAT)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants