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

Bind address for attachment points #442

Open
mlegner opened this issue Jul 10, 2023 · 3 comments · May be fixed by #443
Open

Bind address for attachment points #442

mlegner opened this issue Jul 10, 2023 · 3 comments · May be fixed by #443

Comments

@mlegner
Copy link
Member

mlegner commented Jul 10, 2023

When setting up a SCIONLab AS, it is possible to define a bind address that is different from the public address to support NATed setups.

However, this is only possible for the upstream link to the parent. When making the AS an attachment point, setting a separate bind address for child links is not possible, thus prohibiting setting up NATed attachment points.

This affects both the topology file and the VPN server configuration.

@matzf
Copy link
Contributor

matzf commented Jul 10, 2023

This is indeed a missing feature in the user interface. The admin panel in the background does support defining this bind address, so if you reach out to the scionlab admins, they should be able to help you with a quick workaround.

As far as I can tell, the configuration generated for the openvpn server does not take this into account, though. As a workaround, this can be fixed manually in the generated openvpn server configuration file; the scionlab-config script should keep this file intact.

@mlegner
Copy link
Member Author

mlegner commented Jul 10, 2023

Thanks for the insights, @matzf. It's nothing urgent, for my use case I was able to work around this limitation (e.g., by modifying the OpenVPN setting manually).

I'm happy to contribute a fix if there is interest. 🙂

@matzf matzf linked a pull request Jul 10, 2023 that will close this issue
@matzf
Copy link
Contributor

matzf commented Jul 10, 2023

Aha sure, I've already created a PR in the meantime. This was the second time this question came up, so I figured it should just be fixed. Note that I'm also "just" an outside contributor and no-longer officially working on SCIONLab.

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 a pull request may close this issue.

2 participants