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

Construct the tunnel as a separate phase #8

Open
vanrein opened this issue Jun 2, 2020 · 3 comments
Open

Construct the tunnel as a separate phase #8

vanrein opened this issue Jun 2, 2020 · 3 comments

Comments

@vanrein
Copy link
Owner

vanrein commented Jun 2, 2020

Look at what Tayga does, it has an explicit --mktun command to do nothing but creating the tunnel. This is useful to run as root, especially because tools to do this are getting less common in user space.

@vanrein
Copy link
Owner Author

vanrein commented Jun 2, 2020

Especially interesting is that this usage pattern allows the setup of the network interface by external code, not the builtin ip -6 ... commands that we now need to use. That could greatly simplify our use.

Sure, some information may be derived by the 6bed4router, but that information might then be returned from the --mktun command, perhaps as ENVVAR=value lines or even just the ip -6 ... commands.

@vanrein
Copy link
Owner Author

vanrein commented Jun 2, 2020

Maybe the best thing to do is ensure having the tunnel, not making it. Dropping it could be useful too.

@vanrein
Copy link
Owner Author

vanrein commented Jun 2, 2020

For the TAP mode of #9 it might be good to also have a --mktap or --have-tap variant.

There may be no need to configure if a bridge is used or, dependent on the local setup, configuration may be redirected to a bridge.

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

No branches or pull requests

1 participant