| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
And adopt the tests to add an interface and remove it again.
It should work when deactivating rstp, it will not work when activating
rstp for the first bridge as then the userspace daemon is not yet
available. But once one bridge is active with stp, it should work with
the reload for any further bridge.
Fixes #21745. Also see #22547.
|
| | |
|
| |
|
|
| |
cc #23396
|
| |
|
|
|
|
|
| |
They contain no useful information and increase the length of the
autogenerated options documentation.
See discussion in #18816.
|
| |
|
|
|
|
|
| |
After the change of the bonding options, the examples were not quite correct.
The diff is over-the top because the new `let` needs everything indented.
Also add a small docstring to the `networkd` attr in the networking test.
|
| |\
| |
| | |
nixos: network-interfaces-scripted: don't require mstpd when rstp is off
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
f2fs.fsck depends on crc32 module being present in the initrd system,
otherwise, if f2fs is used as the root disk, the system is unbootable.
|
| |\
| |
| | |
iputils: 20151218 -> 20161105
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
reason: after the upgrade of iputils from 20151218 to 20161105
functionality of ping6 and tracepath6 was merged into ping and tracepath.
Ping is now mostly a drop-in replacment for ping6, except that selecting a
specific interface is done by encoding it into the address (ex.: fe80::1%eth0)
rather then specifing it with the `-I` flag.
|
| | | |
|
| | |
| |
| |
| |
| | |
Also remove some compatibility code because the directory in question would be
shadowed by a mountpoint anyway.
|
| | | |
|
| |\ \
| | |
| | | |
network-interfaces service: fix bindsTo deps for masters
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, netdev units for network interfaces defined in the nixos
configurations would bindTo the systemd device unit of the interface if
not in a container.
In situations where you switch to a new nixos configration with changes
to network-setup.service (like nameservers) and have stacked interfaces
like vlans on a bond, it would fail to propagate restarts to the netdevs
correctly resulting with broken networking. The bond would be present
but no vlan interfaces rendering the machine unreachable.
My fear is that the udev events fail to propagate correctly while a systemd
transaction that is also restarting the triggered netdev service is running.
This commit changes this behaviour so netdev services bindTo other netdev
services if present and otherwise fall back to the previous behaviour.
We also noticed that stacked interfaces would sometimes seemingly be stopped
in the wrong order. For instance in the above example, the bond interface
would be deleted before the vlan interfaces resulting in the vlan interfaces
not being present when their service is being stopped. This would cause the
systemd transaction to fail and thus break networking. Their postStop hooks
are now allowed to fail as we have reached the desired state.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Until now the four attributes available very selectively provided a small
subset, while copying upstream documentation.
We make driver options an arbitrary key-value set and point to kernel
documentation, which is always up-to-date. This way every option can be set.
The four already existing options are deprecated with a warning.
|
| | | |
| | |
| | |
| | | |
Fixes #22470
|
| | | |
| | |
| | |
| | | |
This way we have fonts reloaded on switches.
|
| | |/
|/|
| |
| | |
It was possible to pass empty strings / strings with only separator characters;
this lead to broken fstab formatting.
|
| |\| |
|
| | | |
|
| | |
| |
| |
| |
| | |
Fixes #22470. Also remove non-relevant comment (we don't deviate from upstream
systemd unit anymore).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Regression introduced by 0cb487ee044bbe5cfa1d6421df385b6bc2447bd2.
This changed the result for defaultGateway to be a submodule instead of
just a plain string, so instead of using just cfg.defaultGateway we need
to pass cfg.defaultGateway.address now.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @abbradar
|
| | | |
|
| | |\
| | |
| | | |
glusterfs: add service
|
| | | | |
|
| | |\ \
| | | |
| | | | |
NFS improvements
|
| | | |/
| | |
| | |
| | |
| | | |
* Use /etc/nfs.conf as the recommended upstream way to configure services.
* Move server options to nfsd module.
|
| | |/ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\| |
|
| | |\
| | |
| | | |
zfs: add unstable variant
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Until now nixos only delivered the latest zfs release. This release is often not
compatible with the latest mainline kernel. Therefor an unstable variant is
added, which might be based on testing releases or git revisions.
fixes #21359
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
/etc/hostname is the file used by hostnamectl(1) and the
org.freedesktop.hostname1 dbus service (both provided by systemd) to get
the "static hostname". Better provide it so that users of those
tools/services get a proper hostname.
An example of an issue created by the lack of /etc/hostname is that the
bluetooth stack on NixOS identifies itself to peers as "BlueZ $VERSION"
instead of the hostname.
References:
https://www.freedesktop.org/software/systemd/man/hostname.html
Changes v1 -> v2:
* ensure /etc/hostname ends with a newline
|
| | |/
| |
| |
| |
| | |
Create the file using attrset instead of list, to make it easier to
later provide other files in the same module.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Now the tracking works with aggregated devices on aggregated devices.
So container with physical device where the device is put in a bond
which is the basis for a bridge is now handled correctly.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Test that adding physical devices to containers works, find that network setup
then doesn't work because there is no udev in the container to tell systemd
that the device is present.
Fixed by not depending on the device in the container.
Activate the new container test for release
Bonds, bridges and other network devices need the underlying not as
dependency when used inside the container. Because the device is already
there.
But the address configuration needs the aggregated device itself.
|
| | |\
| | |
| | | |
Replace Network-interfaces.target
|
| | | |
| | |
| | |
| | | |
Ref: 072c1dcc4a319b80ffd4a41165cebacdbb17275a
|