| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | |
|
| | |
| |
| |
| | |
`IPv6PrefixDelegation`
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
This has been there since v209 [1]
```
The interface name to use. This option has lower precedence than NamePolicy=, so for this setting to take effect, NamePolicy= must either be unset, empty, disabled, or all policies configured there must fail. Also see the example below with "Name=dmz0".
Note that specifying a name that the kernel might use for another interface (for example "eth0") is dangerous because the name assignment done by udev will race with the assignment done by the kernel, and only one interface may use the name. Depending on the order of operations, either udev or the kernel will win, making the naming unpredictable. It is best to use some different prefix, for example "internal0"/"external0" or "lan0"/"lan1"/"lan3".
```
[1] https://github.com/systemd/systemd/commit/43b3a5ef61859f06cdbaf26765cab8e1adac4296
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`LinkLocalAddressing`
Both options were introduced in systemd v243[1]. Those options can be
used to ensure that LinkLocalAddressing is only configured for a given
interface if DHCPv4 fails. To quote `systemd.network(5)`:
```
If "fallback" or "ipv4-fallback" is specified, then an IPv4
link-local address is configured only when DHCPv4 fails. If "fallback", an IPv6 link-local
address is always configured, and if "ipv4-fallback", the address is not configured. Note
that, the fallback mechanism works only when DHCPv4 client is enabled, that is, it requires
"DHCP=yes" or "DHCP=ipv4".
```
[1] https://github.com/systemd/systemd/commit/8bc17bb3f707c99b6c9ad295563c92b38141a1f4
|
| |
|
|
| |
(cherry picked from commit ec073e41a0dc8273cd81cf61fa37004310120af2)
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
| |
This follows upstreams renaming of the option [1].
[1] https://github.com/systemd/systemd/commit/9cb8c5593443d24c19e40bfd4fc06d672f8c554c
|
| |
|
|
|
| |
A route via a tunnel interface does not require a gateway to be
specified, so do not check for the Gateway= field on routes at all.
|
| | |
|
| |
|
|
|
| |
Support Multicast= option in [Link] section of network units,
introduced in systemd/systemd#9118.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
nixos/networkd: wait for udev to settle before starting networkd
|
| | |
| |
| |
| |
| | |
... to avoid race condition between udevd renaming and
networkd configuring interfaces (39069)
|
| |/
|
|
| |
This was previously missing.
|
| |
|
|
|
|
| |
This reverts commit d514dc220e9fad27a46ef329360bb8db2cdf22ea.
breaks unpredicable network interfaces: https://github.com/NixOS/nixpkgs/pull/29768#issuecomment-370172863
|
| |\
| |
| | |
networkd: also load builtin modules
|
| | | |
|
| |\ \
| | |
| | | |
nixos/networking-interfaces: add preferTempAddress option
|
| | | | |
|
| |/ /
| |
| |
| |
| | |
Co-Authored-By: Florian Klink <flokli@flokli.de>
Co-Authored-By: Andreas Rammhold <andreas@rammhold.de>
|
| | |
| |
| |
| | |
This reverts commit 8f21e089a8de9eaa2512af25191d17077eca223a.
|
| |/ |
|
| | |
|
| |
|
|
| |
which gained an implementation in systemd v233
|
| |
|
|
|
|
|
|
| |
Since the bonds interface changed to a lot more possible values we create a
mapping of kernel bond attribute names and values to networkd attributes.
Those match for the most part, but have to transformed slightly.
There is also an assert that unknown options won’t slip through silently.
|
| |
|
|
| |
Includes adding some more upstream units and removing obsolete (-.slice) ones.
|
| |
|
|
|
|
| |
networkd options are always correct or up to date. This option allows to by
pass type checking. It is also easier to write because examples can be just copy
and paste from manpages.
|
| |
|
|
|
|
|
|
|
|
| |
Networkd units can contain secrets. In future also wireguard vpn will be supported by
networkd. To avoid leakage of private keys, those could be then also put outside
of the /nix/store
Having a writeable /etc/systemd/network also allows to quick fix network issues,
when upgrading `nixos-rebuild switch` would require network on its own (due
updates).
|
| |
|
|
|
|
|
|
| |
- most nixos user only require time synchronisation,
while ntpd implements a battery-included ntp server (1,215 LOCs of C-Code vs 64,302)
- timesyncd support ntp server per interface (if configured through dhcp for instance)
- timesyncd is already included in the systemd package, switching to it would
save a little disk space (1,5M)
|
| | |
|
| |\
| |
| | |
Replace Network-interfaces.target
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
Systemd upstream provides targets for networking. This also includes a target network-online.target.
In this PR I remove / replace most occurrences since some of them were even wrong and could delay startup.
|
| |
|
|
| |
this is already upstream default
|
| | |
|
| |
|
|
| |
to Network config section
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This shuts up this error from dbus:
May 11 13:52:16 machine dbus-daemon[259]: Unknown username "systemd-network" in message bus configuration file
May 11 13:52:16 machine dbus-daemon[259]: Unknown username "systemd-resolve" in message bus configuration file
which happens because the D-Bus config for networkd/resolved is
enabled unconditionally, and we don't have an easy way to turn it off.
(cherry picked from commit f19b58fb6a5cc55af6d8d8ca7979f8e64255d2d0)
|
| |
|
|
|
|
|
|
|
|
|
| |
During the refactor of the networkd stuff in f8dbe5f, a lot of the
options are now needed by systemd.nix as well as networkd.nix but
weren't moved by that commit as well.
For now, this fixes all networkd VM tests except for the macvlan one and
thus it should fix #7505 for at least DHCP-based configuration.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In f8dbe5f, the default value for networking unit "enabled" option
suddenly flipped to false. I have no idea of whether this happened by
accident, but I'm setting it to true again, because it essentially
breaks systemd networking support and we have systemd.network.enable to
have a "turn the world off" switch.
And of course, because the mentioned commit obviously wasn't done with
even a run of the simplest run of one of the network VM tests, we now
get an evaluation error if we switch useNetworkd to true.
Fixes the core issue of #7505.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| | |
|
| |
|
|
|
|
| |
Otherwise, the enabled -> disabled transition won't be handled
correctly (switch-to-configuration currently assumes that if a unit is
running and exists, it should be restarted).
|
|
|
The systemd module was getting rather bloated.
|