diff options
| author | aszlig <aszlig@redmoonstudios.org> | 2016-07-11 12:01:25 +0200 |
|---|---|---|
| committer | aszlig <aszlig@redmoonstudios.org> | 2016-07-11 12:01:25 +0200 |
| commit | d72823444048e96fb9ad8f682e139655810c95db (patch) | |
| tree | 75d174e25bd77c2d173d51003c77fe32ec1ee705 /machines | |
| parent | bafb5933654cdb7e35f0c54418bdd0dcb999f98c (diff) | |
machines/tyree: Avoid renaming network interfaces
This seems to be related to this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434986 The problem here is a race condition, because NetworkManager is trying to pick up the device _before_ the renaming and then fails to correctly identify it. Another solution would be to reorder the service unit after the networkd service, but that would only work well if the interface is plugged in at boot time and if it's pluggen in/out afterwards we likely have the same problem again. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Diffstat (limited to 'machines')
| -rw-r--r-- | machines/aszlig/managed/tyree.nix | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/machines/aszlig/managed/tyree.nix b/machines/aszlig/managed/tyree.nix index 9a090063..613f8a74 100644 --- a/machines/aszlig/managed/tyree.nix +++ b/machines/aszlig/managed/tyree.nix @@ -43,6 +43,9 @@ networking.networkmanager.enable = true; networking.useNetworkd = true; + # Temporary, seems to be a bug in NetworkManager: + networking.usePredictableInterfaceNames = false; + nix.maxJobs = 4; nix.useSandbox = true; nix.readOnlyStore = true; |