<zhaofeng>
`networking.wireless.enable` adds `wpa_supplicant` to `environment.systemPackages` for you, though you shouldn't need to run it directly
<emmanuel_erc>
and that wpa_supplicant is in the list of environmentPackages?
<emmanuel_erc>
So, I made the mistake of not including wpa_supplicant
<emmanuel_erc>
I don't understand why wpa_supplicant was available during the install stage but wasn't automatically installed when I actually created the system.
<emmanuel_erc>
Hello there. I've just installed nixos on another machine and I'm looking at the manuals and I have no idea how to connect to the internet. For reasons unbeknownst to me, "wpa_supplicant" seems to be entirely missing the usual place where to find installed binaries.
2021-05-11
<erich0>
@hrnz i'm using wpa_supplicant without NetworkManager
2021-05-10
<hyperfekt>
there's a known issue with starting wpa_supplicant with no interface present
<bbigras>
did you set special options for wpa_supplicant?
2021-05-09
<mvnetbiz_>
your user doesn't have wifi privilges, and if you run with sudo, it runs wpa_supplicant as root, but the <() file substitution happens in your user's bash instead of root so it doesn't connect somehow
<QueenUhohsheherv>
Fresh NixOS install. First command `wpa_supplicant -B -i wlo1 -c <(wpa_passphrase 'valid' 'valid')` fails with `Failed to open config file '/dev/fd/63', error: No such file or directory`
<CRTified[m]>
Hi, does anyone has a config for the rpi3b+ at hand where wifi works? According to `ip a` and the wpa_supplicant log, there is a connection, but the RPi is not reachable over wifi and wpa_supplicant also complains about "RRM: Ignoring radio measurement request: Not RRM network". I'm on nixos-21.05pre286925.3e62e383f4b, the RPi is set up with nixops and using linuxPackages_latest (_rpi3 won't build on my x86 host)
2021-04-29
<pennae>
wpa_supplicant does not like being built without pcsclite, despite ostensibly supporting just that
2021-04-17
<Guest80>
it has other variables at the end like "++ optional (!delegateWireless && !enableIwd) wpa_supplicant;"
<uhohqueenofTechl>
So I did `wpa_supplicant -B -i wlp2s0 -c <(wpa_passphrase 'SSID' 'key')`, but that did not work; I `ping google.com` and it does not work.
2021-03-08
<srhb>
jboy: I usually use the nmtui interface for networkmanager instead of direct wpa supplicant because I can never remember if I need to do manual dhcp wrestling when going the low level route.
<jboy>
I've booted from the latest live ISO and I'm trying to install nixos, but even though wpa_supplicant seems to be running fine and connecting to networks, I cannot ping internal IPs, let alone resolve remote addresses. Any ideas what might be going on?
2021-02-27
<{^_^}>
[nixpkgs] @mweinelt pushed to release-20.09 « wpa_supplicant: add CVE-ID for P2P provision discovery proccessing vuln. »: https://git.io/JtNxj
<{^_^}>
[nixpkgs] @mweinelt pushed to master « wpa_supplicant: add CVE-ID for P2P provision discovery proccessing vuln. »: https://git.io/JtNxp
<AlpineLlama>
__monty__: Nah I just remebered how to use wpa_supplicant and went with that. I'll definitely check out iwd if it's the future :). What are it's advantages ?
<AlpineLlama>
__monty__: So in the end I just used straight wpa_supplicant, and now can connect via ssh normaly. Thanks for the help!
2021-02-06
<bqv>
Though I only learnt today that iwd is supposed to deprecate wpa_supplicant, which seems ..weird
<Luker>
Hi. I noted that the last succesful hydra build for raspi4-aarch64 was almost a month ago...any known problems? I have problems with wpa_supplicant and don't know if it's me or the build
<noonien>
hmm, i don't have networking.wireless.enable anywhere in my configuration.nix, yet wpa_supplicant seems to start on boot. is this normal?
2021-01-10
<ZaraChimera>
so I'd add "wpa_supplicant -u" to the extraCmdArgs option?
<ZaraChimera>
Not yet, I just managed to get the wifi card to see the networks around me by manually running wpa_supplicant -u
<ZaraChimera>
So now I just need to tell my system to start wpa_supplicant with the -u flag.
<ZaraChimera>
wpa_supplicant needed to be started with -u flag
<ZaraChimera>
I did add the services.connman.enable = true in configuration.nix and enabled wifi with wpa_supplicant.
<pjt_tmp>
man wpa_passphrase, wpa_supplicant
2021-01-09
<thorn_>
howdy, i just did a fresh install of nixos 20.09, i was able to get wireless working with wpa_supplicant on the liveusb, but now that ive rebooted into my system its unable to pick up that i have a wireless interface. the configuration has networking.interfaces.wlp3s0.useDHCP = true;, which was automatically generated so it was able to see it, im just unsure why its not showing up with ip a now, where would
2021-01-07
<ZaraChimera>
Ran into this issue when using the KDE iso of 20.09: the liveCD saw my WiFi card and I can connect to my SSID, and ping a server through the terminal, but Firefox wouldn't connect to websites. After completing install, the system did not see my WiFi at all. I tried both enabling wpa_supplicant and creating wpa_supplicant.conf and networkmanager. Neither one worked. Using the GNOME iso, networking
2020-12-25
<Gaelan>
On another note: I've got an RPi Zero W that's supposed to connect to wifi on boot. It doesn't, but "sudo systemctl start wpa_supplicant" after boot succeeds
2020-12-18
<{^_^}>
[nixpkgs] @rnhmjoj pushed commit from @fadenb to release-20.09 « nixos/release-notes: Warn on wpa_supplicant changes »: https://git.io/JLBVE
<sphalerite>
if that doesn't work, I'm not sure. Maybe iwd will work better than wpa_supplicant because it's by intel :p
<plfn>
oh, thta's just a fixed set in wpa_supplicant
<plfn>
i'll take a look at that and report back, thanks. one other thing i already noticed, running wpa_supplicant with -d, is a bunch of register frame command failures, with "operation not permitted", but the prefix for those looks like a driver/wifi card id that doesn't match with what i have
<plfn>
i spent some time building a custom iso with the appropriate firmware included, but it turns out the firmware/ucode is already there (in /lib/firmware), so wondering why wpa_supplicant "failed to initialize driver interface"
2020-12-10
<plfn>
i'm trying to install off of the minimal image, but wpa_supplicant fails with "failed to initialize driver interface"
2020-12-01
<{^_^}>
[nixpkgs] @xaverdh opened pull request #105561 → nixos/installation-device: replace wpa_supplicant by iwd → https://git.io/JIJJk
<{^_^}>
[nixpkgs] @jamesluke opened pull request #105521 → nixos/manual: suggest wpa_supplicant command that doesn't fail with sudo → https://git.io/JIvdk
2020-11-22
<{^_^}>
[nixpkgs] @fadenb opened pull request #104589 → nixos/release-notes: Warn on wpa_supplicant changes → https://git.io/JkrzS
2020-11-21
<nasirhm>
__red__: No worries, I fixed it. Actually had to flush my wpa_supplicant configs.
2020-11-17
<ToxicFrog>
nixos-rebuild switch fixes it because it tries to bring the set of running services in line with what's declared in configuration.nix, so it sees that wpa_supplicant isn't running and tries to start it up, and since the system is fully booted now, it works.
<ToxicFrog>
My guess would be: wpa_supplicant depends on something else but hasn't declared that dependency. At boot time, it sometimes tries to start up before the dependency is available, and fails.
<axx>
no wpa_supplicant log :(
<axx>
a 'systemctl restart wpa_supplicant' worked fine, at least
<ToxicFrog>
wpa_supplicant didn't log anything at all? wow, gross
<ToxicFrog>
`journalctl -u wpa_supplicant`
2020-10-26
<bad_sloth>
iwconfig and wpa_supplicant, but all unsuccessful :|
2020-10-21
<pickfire>
So I need to do wpa_supplicant ssid psk separately, then only run the other one, so weird.
<pickfire>
But if I run the subshell first and save that into a file, then run the wpa_supplicant it worked.
<{^_^}>
[nixpkgs] @bendlas opened pull request #96263 → nixos: wpa_supplicant: warn on unused config → https://git.io/JUURm
2020-07-25
<installingNIX>
I naively thought nix would create the conf file for wpa_supplicant but than you colud manually edit them and it would be erase at the next rebuild
<clever>
installingNIX: personally, i use naked wpa_supplicant, with /etc/wpa_supplicant.conf not managed by nix
<installingNIX>
the only way would be to go throw wpa supplicant?
2020-07-15
<nij>
I believe to make wpa_supplicant work one must become root.
<nij>
I created passwd for the default user nixos, and created a passwd for root. I logged into root, and ran `wpa_supplicant -i wls1 -c <(wpa_passphrase "SSID" "PASSWORD")`
<nij>
Hello! New to nixOS. Just bought a new hard disk and am trying to install on a minimal interface. I'm folloing the official doc has no luck connecting to the Wifi via wpa_supplicant.. there are several trouble shoots online too. Tried.. with no luck either. Would anyone help?
2020-07-09
<AlpineLlama>
haven't enabled it yet. for the moment I just had wpa_supplicant
2020-07-06
<KarlJoad>
That did not seem to solve the problem. I think it might be related to WPA supplicant though.
2020-07-03
<nh2[m]>
etrigan63: in the first file, `networking.networkmanager.enable = true;` and `networking.wireless.enable = mkForce false;` (disabling direct use of wpa_supplicant, probably so that network-manager can rule the device)
2020-06-28
<pax-12>
Jun 28 20:24:22 nixos-box wpa_supplicant[5479]: Failed to read or parse configuration '/etc/wpa_supplicant.conf'.
<pax-12>
Jun 28 20:24:22 nixos-box wpa_supplicant[5479]: Failed to open config file '/etc/wpa_supplicant.conf', error: No such file or directory
<pax-12>
Jun 28 20:24:22 nixos-box wpa_supplicant[5479]: Successfully initialized wpa_supplicant
<pax-12>
Jun 28 20:24:22 nixos-box systemd[1]: Started WPA Supplicant.
<pjt_mpt>
happyfishes: wpa_supplicant isn't too hard to use
2020-06-16
<bennofs[m]>
i am a bit confused, there's both networking.supplicant and networking.wireless. Both of them seem to configure wpa_supplicant, which one should I use?
2020-06-15
<euank>
but if you can get wpa_supplicant to work, that seems simpler
<Jonathan92>
Hey everyone, I am new to nix and doing an install from the minimal image. I am having issues getting my network setup. There seems to be an issue with overly long names in wpa_supplicant https://github.com/benzea/gnome-network-displays/issues/70 . It looks like the solution is to enable net.ifnames = 0, but I am not sure which .nix file to add
<etu>
I don't think they do... but not sure... but wpa_supplicant won't give as nice of a user interface as networkmanager
<energizer>
LevelChart8: "networking.wireless.enable = true;" means wpa_supplicant not networkmanager
2020-05-28
<klys>
yes, network-manager runs wpa-supplicant.
<jakobrs>
I noticed that I have both NetworkManager and wpa_supplicant running; is this normal?
2020-05-17
<{^_^}>
[nixpkgs] @jtojnar pushed to master « wpa_supplicant_gui: fix build with Inkscape 1.0 »: https://git.io/Jf0D9
2020-05-10
<clever>
morgrimm: ah, its done by wpa_supplicant via that line
<clever>
matthewcroughan: i enable wpa_supplicant, but i dont give configuration.nix the pw
<matthewcroughan>
Okay, so I've gotten to generating my first configuration.nix, how would I specify my wpa_supplicant user/pass in there?
<clever>
matthewcroughan: wpa_passphrase 'SSID' 'key' | sudo tee -a /etc/wpa_supplicant.conf ; sudo wpa_supplicant -B -i interface -c /etc/wpa_supplicant.conf
<ex-parrot>
so you'd need to run "wpa_passphrase foo bar" first, which outputs the config for wpa_supplicant, then put that in a file, then wpa_supplicant -c ./path/to/file
<ex-parrot>
in the docs you'll note they don't use sudo, so the wpa_supplicant and wpa_passphrase are both running as the same UID (which it, perhaps wrongly, assumes you'll know needs to be in a root shell)
<matthewcroughan>
I would be able to run wpa_supplicant as root and this issue wouldn't present itself, is this not true?
<ex-parrot>
if you want to use sudo you need to explicitly do something like "sudo wpa_supplicant -B -i interface -c <(sudo wpa_passphrase 'SSID' 'key')"
<matthewcroughan>
The other ones, I got over, but this one is genuinely confusing, I've never even used wpa_supplicant's cli before, to be honest, only its configuration files.
<matthewcroughan>
Does anybody want to inform me as to how to get that wpa_supplicant command working in the nixOS installer?
<matthewcroughan>
uh, so I'm following the guide now up to the point of wpa_supplicant
<matthewcroughan>
e.g it's telling you to use wpa_supplicant, and I know that this is configuring networking, but how am I supposed to know NixOS isn't configured to allow the user to manage this?
2020-05-02
<Setzer22_2>
When I run "nixos-rebuild switch" on my machine, I'm getting a systemd error restarting wpa_supplicant: Failed to open config file '/etc/wpa_supplicant.conf', error: No such file or directory
2020-04-30
<Raito_Bezarius>
<metasyntactical> stop networkmanager service, focus only on wpa supplicant
<clever>
metasyntactical: you used nmcli to connect, but wpa_supplicant should already be connecting
<clever>
metasyntactical: stop using network manager commands, wpa_supplicant only
<clever>
metasyntactical: wpa_supplicant must be ran as root, or nothing will work at all
<clever>
metasyntactical: wpa_supplicant must be ran as root, or nothing will work at all
<clever>
metasyntactical: add that, and restart wpa_supplicant
<clever>
try stopping nm, and then just manually run it, something like: wpa_supplicant -s -u -Dnl80211,wext -c /etc/wpa_supplicant.conf -iwlp3s0
<clever>
enless you stop network manager, and manually re-launch wpa_supplicant
<clever>
metasyntactical: if i lsof the pid of wpa_supplicant, i can see that its listening on a unix socket in that dir
<clever>
check the args to wpa_supplicant itself, what file is it using? is the ctrl_interface diff?
<metasyntactical>
could not connect to wpa_supplicant
<energizer>
nm is getting an alternate backend "iwd" to replace wpa_supplicant
<clever>
metasyntactical: i just always use wpa_supplicant bare, with wpa_supplicant.conf un-managed, and it has worked great
<clever>
Raito_Bezarius: pretty sure you will always have wpa_supplicant, because network-manager uses wpa_supplicant behind the scenes
<Raito_Bezarius>
write a wpa_supplicant minimal conf
<metasyntactical>
I have wpa supplicant
<Raito_Bezarius>
do you still have a wpa_supplicant?
2020-04-25
<genevino>
btw i was unable to get network-manager to work (not a joke) but setting up wpa_supplicant manually worked like a charm.
2020-04-23
<gerschtli>
Jaxon: i dont know, i cant see the errors :D but you could use a lan cable or just use wpa_supplicant, see the nixos manual install section
2020-04-02
<guest1234>
I'm an aspiring nix user that's stuck at the install screen. I have an old x220, but no ethernet cord to connect it directly. I've created a wpa_supplicant.conf file and restarted wpa_supplicant. running the command wpa_cli seems to show that I'm connected to my wifi. When I run nixos-install I'm still shown the message "warning: you don't have
2020-03-25
<lassulus>
networkmanager uses wpa_supplicant
<energizer>
i am running networkmanager but i notice that wpa_supplicant is also running. why is this happening?
<energizer>
i just noticed in pstree that wpa_supplicant is running. i already have network-manager going. why is wpa_supplicant still here?
2020-03-21
<sleeping->
trying to install nixos on my thinkpad x1e gen2. i cant get wifi to work so i cant install. running wpa_supplicant -B -i enp0s31f5 -c CONFIG gives me nl80211 driver does not support authentication
<energizer>
i dont seem to have wpa_supplicant or nmcli
2020-03-14
<danderson>
careful, wpa_supplicant only connects you to the wifi network, it doesn't do DHCP :) You need to run `dhcpcd` separately
<blibberblob>
it fails with a wpa_supplicant error
<blibberblob>
hmm, adding that extraModulePackages didn't work... wpa_supplicant failed to start
2020-02-08
<electrocat>
wpa_supplicant is broken in the latest nixos version for me :/ anyone else having issues?
2020-01-31
<wild_buffalo>
and the machine reconnects to the network---I'm assuming via wpa_supplicant
<wild_buffalo>
Now it seems they're conflicting---how do I deactive wpa_supplicant?
<wild_buffalo>
so I've installed nixos with wpa_supplicant at first
2020-01-27
<arcnmx>
I think it stopped around the time I switched from using connman+wpa_supplicant to connman+iwd but not sure if anything else in my system config may have changed around then too...
2020-01-23
<infinisil>
hpfr[m]: Oh no you can't use wpa_supplicant and networkmanager together, unless you want to use them for different network interfaces
<infinisil>
(using wpa_supplicant)
2020-01-21
<eoli3n_>
i think that connman services installed wpa_supplicant
<eoli3n_>
when i rebuild i always have a problem with wpa_supplicant which can't restart
2020-01-20
<evanjs>
from the wiki: "To manually configure the wifi on the minimal installer, run wpa_supplicant -B -i interface -c <(wpa_passphrase 'SSID' 'key').
<Vikingman>
only wpa_supplicant as i know
2020-01-14
<eoli3n>
but connman+wpa_supplicant should work
<eoli3n>
i could change connman to use iwd instead of wpa_supplicant
<eoli3n>
trying to install my laptop, and to run wpa_supplicant with connman
2020-01-11
<clever>
ambro718: wpa_gui can control wpa_supplicant i believe
<clever>
ambro718: i know how to use wpa_supplicant
2020-01-02
<lunik1>
I am trying to switch from NetworkManger to connman, and I have added networking.connman.enable = true to my configration. But now wpa_supplicant fails to start because there is no /etc/wpa_supplicant.conf. What am I missing?
2019-12-07
<MichaelRaskin>
Complicated eduroam setup? There is a high chance that they actually provide a script somewhere which can be pried open to extract wpa_supplicant network block! Good luck fighting the today's version of UI
<`_>
In my case, yes, wpa_supplicant does everything automatically behind my back which is great, but I'd rather not have those PSKs in my public configuration.nix
<MichaelRaskin>
Because open networks, wpa_supplicant takes them automatically
<clever>
notgne2: it probably auto-detects all interfaces, i just use plain dhcpcd and wpa_supplicant
2019-11-22
<waleee-cl>
the first one uses wpa_supplicant and the other is self-explanatory
<jared-w>
Does your wpa_supplicant file exist?
<zeta_0>
when i set the option: `networking.wireless.enable = true;` in configuration.nix, wpa_supplicant threw an error: `Failed to open config file '/etc/wpa_supplicant.conf', error: No such file or directory`
2019-11-17
<clever>
so if i reboot, wpa_supplicant can no longer start
<clever>
but, the act of loading bonding, breaks wpa_supplicant
<clever>
kolbycrouch: normal wpa_supplicant
2019-11-12
<clever>
2019-11-12 04:27:23 < clever> Nov 12 04:23:15 system76 3s0avjla52qx9zx8yi6glba43did5bvq-unit-script-wpa_supplicant-start[7893]: /nix/store/3s0avjla52qx9zx8yi6glba43did5bvq-unit-script-wpa_supplicant-start: line 4: /sys/class/net/bonding_masters/uevent: Not a directory
<__monty__>
gchristensen: ^ managed to fix my issue with bonding and wpa_supplicant.
<__monty__>
How would I go about finding where a certain wrapper script is created? `/nix/store/$hash-unit-script-wpa_supplicant-start` in this case.
2019-11-10
<__monty__>
Question about setting up bonding. Somehow wpa_supplicant ends up configured wrong: http://ix.io/214y
2019-11-07
<__monty__>
Ok, so I'm trying to fix this wpa_supplicant issue: http://ix.io/2100 This is the part of my configuration.nix relevant to networking: http://ix.io/2108 And this is the service file from the nix store that causes the problem: http://ix.io/214k It's looping over all devices and somehow picking up my bond even though it shouldn't, afaict. Do I understand this correctly? And if so, how do I influence the
<rotaerk>
clever, got the wifi working. using that ISO fixed everything except one thing: I'd never used wpa_supplicant before and I didn't bother to actually understand the arguments, so I didn't realize I was supposed to put the acctual interface name after -i ... fixed that
<clever>
but then sudo wont pass that pipe on to wpa_supplicant
<rotaerk>
would `wpa_supplicant -B -i interface -c <(wpa_passphrase 'SSID' 'key')` work with WPA2 or do I need to do additional work for that
<rotaerk>
hmm yay, my network connection didn't come up, and wpa_supplicant isn't working
2019-11-06
<gchristensen>
__monty__: my thinking is you probably need to use wpa supplicant on the bond slave instead of the bond itself
<gchristensen>
__monty__: you probably can't use wpa_supplicant on a bond
<__monty__>
Anyone familiar with bonded interfaces and wpa_supplicant? http://ix.io/2100
2019-11-02
<colemickens>
(Of course, when I first said IWD there, I meant wpa_supplicant.)
* colemickens
can't wait until systemd-networkd plays nice with IWD. Leave wpa_supplicant behind us where it belongs
<Jonathan66>
@bdju I can help you setup network-manager if all you are looking for is internet. For wpa_supplicant someone else will need to advise.
<Jonathan66>
@bdju I have never actually used wpa_supplicant (directly at least). I use network-manager for my WiFi. Do you need wpa_supplicant specifically?
<bdju>
I'm on a fresh unstable install and I can't seem to get wifi with wpa_supplicant working. I tried declaring my home network in my system config, but also wpa_cli can't connect to wpa_supplicant so I can't try it manually either
<clefru>
Is there a way to talk to wpa_supplicant via wpa_cli when run regularly from NetworkManager? I can't seem to find the control socket for it, also I don't see it having any config file on the command line. It looks like it is spawned with "wpa_supplicant -u" for control via dbus, but how do I hook up wpa_cli with dbus?
2019-08-16
<clever>
freedan42x: restart wpa_supplicant any time you change the config file
<freedan42x>
jasom, isn't that annoying each time restart wpa_supplicant?
<jasom>
freedan42x: should be able to just restart wpa_supplicant to fix that, right?
2019-08-14
<sphalerite>
timokau[m]: well it works with plain wpa_supplicant
<sphalerite>
I want to enable network-manager on a laptop that's currently using plain wpa_supplicant. Trouble is, (a) I don't currently have physical access to the laptop, and (b) my only access to it is _via_ the wifi it's currently connected to. Does anyone have any wonderful ideas how I could do this safely?
2019-07-23
<infinisil>
inquisitiv3: Look at the full logs with `journalctl -u wpa_supplicant -e`
2019-07-21
<rnhmjoj>
if nm and wpa_supplicant are incompatible enabling both should raise an error, we could add an assertion maybe. i'll open an issue
<rnhmjoj>
run systemctl status wpa_supplicant
<rnhmjoj>
is wpa_supplicant running?
2019-07-14
<Miyu-chan>
Also, that should be handled by wpa_supplicant, but I don't know how to test it.
<Thra11>
The manual says that setting `networking.wireless.enable = true;` will start wpa_supplicant, but I can see absolutely no sign of it even having tried to start it.
<Thra11>
I have network.wireless.enable = true; and I've set a network. How can I debug why it isn't working? There's no mention of wpa or wlan in the journal. The wpa_supplicant service status is inactive.
<day|flip>
iwd is a replacement to wpa_supplicant
2019-07-03
<TheGamingBarrel>
Well, first of all, don't try to use wpa_supplicant or anything else with networkmanager, they'll trip over each other, AC 9560 is being shown therefore it's supported, does `nmcli device wifi list` show your local SSID's?
<aanderse>
did wifi work with wpa_supplicant?
<allenj12>
no, mostly the generated starter config, got rid of the wpa_supplicant enable tho
2019-07-02
<allenj12>
hmm the default enable.wireless fails trying to read the wpa_supplicant config file
2019-07-01
<dminuoso>
Mmm, whats the canonical way to do WPA2 enterprise with nixos? It seems I cant use nm together with wpa_supplicant sadly.
2019-06-26
<day|flip>
then why is it im have to manual restart wpa supplicant to get my wifi to popup?
<clever>
it started both connman and wpa_supplicant at exactly 17:17:57
<day|flip>
it look like wpa_supplicant not starting
<day|flip>
wpa_supplicant start. but connman cant connect. untill i restart wpa_supplicant
<colemickens>
I'm not really sure how wpa_supplicant and connman are expected to interact in NixOS currently, but generally, Systemd has facilites for making services wait on one another.
<day|flip>
will the problem is wpa_supplicant does not connect the frist time as it boot. since connman need it running. it just does not fully start
<day|flip>
connman need wpa_supplicant to start for it to work with wifi. but for some reason wpa_supplicant does not start on boot. i have to manual start it. for connman wifi to work
2019-06-16
<linux_>
After running wpa_supplicant I still can't ping anything in the internet
2019-06-12
<clever>
back in my day, network-manager didnt exist, and i had to figure out wpa_supplicant without internet access, just to get internet working!
<clever>
mac10688: it has a bit of trouble switching, try restarting wpa_supplicant again?
<eyJhb>
And also, for some reason it somewhat broke my entire system when I used wpa_supplicant
<eyJhb>
teto the only place where it could be, might be extraconfig. But, it would be nice if you could configure wireless networks like i wpa_supplicant package.
<eyJhb>
Is it possible to configure networkmanager from .nix, like wpa_supplicant?
<eyJhb>
I just disabled networkmanager and enabled wpa_supplicant. Like. Nothing worked after that reboot, quite weird
<clever>
then you will want to bring the IF up (ip link set XXX up), then run wpa_supplicant with &
2019-05-03
<jchia_>
I just did a basic NixOS installation following the manual. However, the system is missing some important things. I can't connect to wifi because there's no wpa_supplicant. There's no vim, so I can only use nano. I think I need network connection above all. Supposing I have no Ethernet, does this mean I have to boot back to the USB and reinstall with a modified config that include the packages I need, including wpa_supplicant? If I have E
<WilliamHamilton>
should I stop the wpa_supplicant before?
<qyliss>
You might have better luck with that than wpa_supplicant. It's a lot higher-level and friendlier.
<WilliamHamilton>
systemctl status wpa_supplicant returns among other things active(running)
<qyliss>
What does sudo systemctl status wpa_supplicant say?
2019-04-30
<gentauro>
(maybe it's a bit onfair cos I have a physical cable, instead of using wifi. Could guess that the wpa_supplicant could give some problems)
<samueldr>
probably something like wpa_supplicant and dhcpcd/dhclient
2019-03-23
<noonien>
in the past i was not able to get wpa_supplicant and sshd to start on boot, even by setting their "wantedBy" systemd service option
<noonien>
it starts wpa_supplicant
<srhb>
noonien: Does systemctl start wpa_supplicant also fail_
<noonien>
any reason why this config (http://vpaste.net/GrsFK) on a rPI 3B+, does not have `sshd`, and `wpa_supplicant` in `systemctl list-units --all`, while both `wpa_supplicant.service` (http://vpaste.net/t73eT) and `sshd.service`(http://vpaste.net/MSajp) exist in /run/current-system/etc/systemd/system/?
2019-03-22
<noonien>
a reboot, and a daemon-reload still doesn't show wpa_supplicant in systemctl list-units --all
<infinisil>
And then `systemctl status wpa_supplicant`
<srhb>
noonien: Does it even have a log? sudo journalctl -u wpa_supplicant
<noonien>
i'm trying to get wifi on boot on a rPI 3B+, this is my config: http://vpaste.net/GrsFK, wpa_supplicant doesn't seem to start
<monokrome>
So, the issue w/ wpa_supplicant is that the network package doesn't automatically create wpa_supplicant.conf
<colemickens>
It's possible that wpa_supplicant doesn't even read from the file you wrote.
<colemickens>
aside: I think NM can use IWD as a backend now though, but I guess wpa_supplicant has never hurt me.
2019-03-21
<oldandwise>
i have a Samsung Wifi USB dongle (which i tested working when inserted in another linux laptop). But it's causing my nixos wpa_supplicant to shutdown and i lost wifi. `lsusb` and `dmesg` can see it, somehow it felt like it is conflicting my existing wlp3s0. Logs shows https://termbin.com/kxqs
2019-03-19
<jtojnar>
scientist: it is replacement for wpa_supplicant, I remember there was some bug that it set networking.wireless
<scientist>
how do i set wpa_supplicant in my configuration.nix , i want to enable wifi ?
2019-03-02
<srhb>
I tend to use it simply to get nmtui during installs, so I don't have to muck about with wpa supplicant.
<leotaku>
linarcx: honestly using wpa-supplicant is a huge PITA if you don't know exactly what you are doing. If you have an ethernet cable/jack try using that if possible.
<linarcx>
guys. i cant connect to internet after try: wpa_supplicant -B -i interface -c <(wpa_passphrase 'SSID' 'key') in minimal iso. what should i do?
<averell>
linarcx: assuming your wpa_supplicant command succeeded you could try running "dhcpcd"
<linarcx>
Hi. I'm planning to install nixos from minimal iso into hard disk. So I Burn it into a USB flash drive, and follow the manual on the nixos website. In section 2.1.1 it says that to configure wifi internet you must enter this command: wpa_supplicant -B -i interface -c <(wpa_passphrase 'SSID' 'key'). After I enter, it says: Successfully initialized wpa_supplicant. But I can't ping any web site like Google. It says: Ping www.google.com : name or service
2019-02-23
<{^_^}>
[nixpkgs] @xeji pushed commit from @delroth to master « wpa_supplicant: 2.6 -> 2.7 (#55926) »: https://git.io/fhbYH
<ar1a>
either use wpa_supplicant or network manager
<laas>
to restate my problem: dmesg says nothing and wpa_supplicant gives no errors. I'm using 4.20.10 with unfree drivers too. Running `ip a` shows me that I'm connected but it only shows a link/ether field and an inet6 field
2019-02-20
<lassulus>
yes, wpa_supplicant, you need to create /etc/wpa_supplicant.conf manually
<disasm>
reallymemorable: just run that wpa_supplicant command
<malice`>
I couldn't run wpa_supplicant. I guessed (correctly) that it was due to the network-manager running, so I stopped it. I succeeded, but I don't have dhcp server running anymore. How do I start one? dhcpcd wasn't working.
<lejonet>
Ariakenom: I would also give you a hint to look at iwd, if you don't like networkmanager and think wpa_supplicant is too much work
<Ariakenom>
I suppose the live CD was using networkmanager but the tutorial recommended wpa_supplicant?
<clever>
Ariakenom: then you just need to run wpa_passphrase, and feed the resulting config into /etc/wpa_supplicant.conf, or abandon supplicant and use NM
<noonien>
i don't really like using wpa_supplicant