New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow NetworkManager and wireless together #64364
Conversation
@@ -173,13 +173,24 @@ in { | |||
''; | |||
}; | |||
|
|||
withSupplicant = mkOption { | |||
internal = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about the internal here. Also we could use a more generic option like "ignoreWireless"/ "delegateWireless" without naming supplicant as there might be other options in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not exactly sure about the semantics of internal
.
Actually I think I want it to be just a variable.
Is internal like a config option that the user cannot set themself, just the module?
Yeah okay, not calling it supplicant makes sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I switched to a variable with the name delegateWireless
.
8f34186
to
699bb98
Compare
8afa5f5
to
9ab92c1
Compare
9ab92c1
to
6790ead
Compare
When NetworkManager is configured to not manage all interfaces, it's perfectly fine to have the rest be managed by the standard nixos wireless scripts. I use networking.networkmanager.unmanaged = [ "*" "except:type:wwan" "except:type:gsm" ]; to control everything using networking.wireless except for the mobile LTE modem which only works with NetworkManager.
6790ead
to
b4044a3
Compare
Rebased on top of master. |
Incorrect merging of modules resulted in dhcpcd being enabled causing flaky network connection. NixOS#64364 Fixing it uncovered an infinite recursion from the same commit, previously masked by the incorrect merge. We can just drop the `mkDefault` for `networking.wireless.enable` as it is already `false` by default. Closes: NixOS#72416
Incorrect merging of modules resulted in dhcpcd being enabled causing flaky network connection. NixOS#64364 Fixing it uncovered an infinite recursion from the same commit, previously masked by the incorrect merge. While this is not a problem in 19.09, we can still drop the `mkDefault` for `networking.wireless.enable` as it is already `false` by default. Closes: NixOS#72416 (cherry picked from commit 894fdfa)
Incorrect merging of modules resulted in dhcpcd being enabled causing flaky network connection. NixOS#64364 Fixing it uncovered an infinite recursion from the same commit, previously masked by the incorrect merge. We can just drop the `mkDefault` for `networking.wireless.enable` as it is already `false` by default. Closes: NixOS#72416 (cherry picked from commit 894fdfa)
Motivation for this change
When NetworkManager is configured to not manage all interfaces, it's
perfectly fine to have the rest be managed by the standard nixos
wireless scripts.
I use something like this:
to control everything using networking.wireless except for the mobile
LTE modem which only works with NetworkManager.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)