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

Exit gc NAT and static ip support #1001

Open
jkilpatr opened this issue Sep 30, 2024 · 0 comments
Open

Exit gc NAT and static ip support #1001

jkilpatr opened this issue Sep 30, 2024 · 0 comments
Assignees

Comments

@jkilpatr
Copy link
Member

Exits should have a config that accepts a public ipv4 subnet assigned to the router. From there the internal ip range should be split evenly across these ip, then when clients connect they should be round robined between these internal subnets to load balance them across the public ip range.

Some ip's could also be reserved to provide clients with static ip support, where that client upon connecting would have a single route for their ip.

What makes this more interesting/challenging is that exits have a large list of clients, many of which will never be seen on this exit, so we need to configure and assign ip only as clients actually show up.

This will also need dashboard support so it can be configured by operators.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant