Skip to content

One tenant can evict other tenants' NAT sessions #721

Closed as not planned
Closed as not planned

Description

@privateip

Summary

Every tenant on an egress shard shares one session table of 65,536 entries for NAT66 and NAT64, with no per-tenant limit. When it fills, the oldest sessions are evicted whoever owns them, so one tenant opening connections fast enough breaks the live connections of every other tenant on that shard.

Tenants also cannot see how many sessions they hold. #684 lists a per-tenant limit and per-tenant visibility as phase 1 goals, and today the shard only counts drops for itself as a whole.

Acceptance criteria

  • A tenant at its session limit is refused new sessions, and other tenants' existing sessions on that shard keep working
  • A tenant can see its current NAT session count and its limit
  • An operator can see which tenant reached its limit and when

Activity

  1. added
    bugSomething isn't working
    priority/highHigh priority bug — should be fixed before next release
    on Oct 4, 2026
  2. added
    needs triageIssues that need to be triaged before implementing
    and removed
    needs triageIssues that need to be triaged before implementing
    on Oct 4, 2026
  3. added theissue type on Oct 4, 2026
  4. removed
    bugSomething isn't working
    priority/highHigh priority bug — should be fixed before next release
    on Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Fields

    Priority

    High

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions