Skip to content

Support empty ips/as_range with non-empty nots/not_as #662

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

qmonnet
Copy link
Member

@qmonnet qmonnet commented Jul 1, 2025

In progress - blocked by #661

The user API supports VpcExpose configurations with empty "ips"
(respectively "as_range") but non-empty "nots" (respectively "as_not").
To support this in the dataplane, we need to add a root prefix to the
list of allowed prefixes when we optimise the expose object.

Signed-off-by: Quentin Monnet <[email protected]>
@qmonnet qmonnet self-assigned this Jul 1, 2025
@qmonnet qmonnet added the area/nat Related to Network Address Translation (NAT) label Jul 1, 2025
qmonnet added 2 commits July 2, 2025 01:38
This reverts commit e296c01.

Following recent changes in the NAT code, in particular the removal of
the "not" and "not_as" blocks from the internal NAT configuration
object, we now support configuration with exclusion prefixes only, and
can revert this commit where we rejected it during validation.

Signed-off-by: Quentin Monnet <[email protected]>
Make sure that we process expose objects containing exclusion prefixes
only as we expect.

Signed-off-by: Quentin Monnet <[email protected]>
@qmonnet qmonnet force-pushed the pr/qmonnet/support-empty-allowed branch from 936ecd0 to 25e1799 Compare July 2, 2025 00:40
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.

1 participant