cjdns declarative configuration #3241
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 |
ehmry
force-pushed
the
cjdns
branch
2 times, most recently
from
1450fcd
to
2564161
Compare
|
I need to update the cjdns revision for the package, but I have to work out an issue with the service module. |
ehmry
force-pushed
the
cjdns
branch
2 times, most recently
from
bde0917
to
05bba2a
Compare
systemd service wants network-interfaces.target rather than network.target assertion on config.networking.enableIPv6
|
I had the systemd unit want network.target when it should have wanted network-interfaces.target (like OpenVPN), because of that CJDNS would not connect to peers reliably and that is now fixed. I've also updated the package, which was almost 6 months out of date. |
7c6f434c
added a commit
that referenced
this pull request
Sep 1, 2014
cjdns declarative configuration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At present the cjdns service reads a user generated config from /etc.
This PR generates the node secret key and stores it in /etc, and embeds the rest of the configuration in the systemd unit. The secret is not updated until it goes missing from the file.
In this way the same configuration can be copied between machines without addresses clashing.