9ccc369ff3
These networks are not connections to upstream routers, but where we are ourselves are the upstream router, hence it doesn't make too much sense to require them to be up as default to determine if we are "online", because they lead "in the wrong direction". Also, disable DHCP lease persistency for these networks, since container/VM/namespaces are generally shortlived, and typically have no persistent identity. Moreover, the IP range we assign each VM/container connection is just too small to permit persistency, as otherwise we'll run out of leases way too quickly if VM/containers are restarted a bunch of times with different MAC addresses (which I ran into). I think these are better defaults, but of course these are only defaults.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS