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.

Sign up for GitHub

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

Jump to bottom

Border router / SCION services should wait for tun0 interface if needed #206

Closed
mkowalski opened this issue Oct 24, 2019 · 2 comments
Closed

Border router / SCION services should wait for tun0 interface if needed #206

mkowalski opened this issue Oct 24, 2019 · 2 comments

Comments

@mkowalski
Copy link
Contributor

As a user I need to be sure OpenVPN connection is ready before I start SCION services. As [email protected] finishes activation before the VPN connection is ready, we cannot rely on a simple systemd-service dependency.

Systemd syntax to achieve that is as follows

BindsTo=sys-devices-virtual-net-lan0.device
After=sys-devices-virtual-net-lan0.device

Related-bug: #190
@mkowalski
Copy link
Contributor Author

The solution is not so straightforward as we do not statically define tun0 to be the interface, thus we cannot simply hardcode the dependency on the systemd device.

@mkowalski mkowalski mentioned this issue Nov 13, 2019
Closed
@matzf
Copy link
Contributor

matzf commented Oct 6, 2020

C.f. discussion in related PR.

@matzf matzf closed this as completed Oct 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

WIP: Start OpenVPN client when starting scionlab.target netsec-ethz/scionlab
2 participants
@mkowalski @matzf