systemd dependencies on SIG

scion-backbone / sbas

Prototype implementation for the Secure Backbone AS (SBAS) routing system.

0 stars 1 forks source link

systemd dependencies on SIG #36

Open joelwanner opened 3 years ago

joelwanner commented 3 years ago

With the current structure of systemd units, there are some problems:

When the SIG is restarted (but not SBAS), the address (on the sig device) required for the GRE tunnels disappears
When SBAS is restarted, configuration changes related to the SIG are not applied

We could either create a systemd target to resolve this, or use a workaround (e.g., adding the address not to the sig device, but to loopback instead)

joelwanner commented 3 years ago

Proposed structure for target-based setup:

sbas.target
|- sbas.unit (simply generates configurations)
|  |- docker container
|  |- scion-ip-gateway
|  |- router

This can be implemented using the WantedBy=sbas.target and PartOf=sbas.target directives.