2017-06-17

<MichaelRaskin> That's the trouble — you invest half an hour once, then wpa_supplicant is actually simpler _and it stays the same over years_
<turion> MichaelRaskin: I understand that viewpoint, but I'm happy I can use networkmanager to just connect to a network quickly without having to mess around with wpa_supplicant directly (as long as there is a way to get rid of it quickly)

2017-06-03

<tanonym> Okay, wpa_supplicant is not functioning as expected any more. Service fails with a 255 exit cod
<tanonym> Hm, something went wrong with the networking now. Enlightenment does not enable connman, and something is screwy when I try to get wpa_supplicant to enable. I´ve added ctrl_interface = DIR = /run/wpa_supplicant GROUP = wheel to /etc/wpa_supplicant.conf
<deba5e12> systemctl status wpa_supplicant reports it as up and running
<deba5e12> I thought I had systemd set up to launch it, but i'm a bit unsure. I have networking.wireless.enable = true; in my config -- it was there in the default config file, with a comment saying that it enables wireless using wpa_supplicant.
<clever> deba5e12: did you use the wpa_supplicant service in systemd, or manualy launch wpa_supplicant?
<ertes> i'm currently using wpa_supplicant (via networking.wireless), but i'd like to switch to networkmanager

2017-06-02

<pseudo-sue> wpa_supplicant seems to be failing on boot, and I think this is due to missing firmware. what needs to be in my configuration.nix to get, say, iwlwifi?
<capisce> what I did before was wpa_supplicant -B -i interface -c <(wpa_passphrase 'SSID' 'key')
<clever> anything in "journalctl -f -u wpa_supplicant" ?
<clever> capisce: stop it, then run "systemctl start wpa_supplicant"
<capisce> manually started wpa_supplicant
<clever> capisce: did you run the wpa service or manualy start wpa_supplicant?
<capisce> I'm trying to install nixos on a laptop via wifi, wpa_supplicant managed to connect but doesn't get an ip address

2017-05-30

<clever> shnupta: depends on if you prefer wpa_supplicant or networkmanager
<clever> shnupta: run "wpa_passphrase <networkname> <password> >> /etc/wpa_supplicant.conf" and then restart the wpa_supplicant service in systemd

2017-05-23

<tanonym> Okay, now wpa_supplicant is running.
<bennofs> tanonym: can you pastebin journalctl -u wpa_supplicant?
<bennofs> tanonym: try systemctl start 'wpa_supplicant@your_wifi_interface_name'
<tanonym> May 23 01:26:27 nixos wpa_supplicant[1734]: Successfully initialized wpa_supplic
<tanonym> May 23 01:26:27 nixos systemd[1]: Started WPA Supplicant.
<tanonym> ● wpa_supplicant.service - WPA Supplicant
<bennofs> tanonym: systemctl status wpa_supplicant ?
<tanonym> I ran systemctl start wpa_supplicant and then ran the ps aux command again, same output
<bennofs> tanonym: is that the only output? that would mean that wpa_supplicant isn't even running?
<tanonym> 1731 1.0 0.0 119824 2220 pts/1 SN+ 01:24 0:00 grep wpa_supplicant
<bennofs> tanonym: ps aux | grep wpa_supplicant
<bennofs> tanonym: what supplicant.conf did you check? I think nixos invokes wpa_supplicant with an explicit config file
<tanonym> Hm, I may have to rebuild nixos's wpa_supplicant then?
<bennofs> " -u Enable DBus control interface. If enabled, interface definitions may be omitted. (This is only available if wpa_supplicant was built with the CONFIG_DBUS option.)
<bennofs> from man wpa_supplicant:
<bennofs> tanonym: does conman perhaps use wpa_supplicant's dbus interface?
<tanonym> Now that wpa_supplicant file I need.
<tanonym> connmanctl scan wifi throws the unsupported technology error. Which according to ArchWiki is because I didn't star wpa_supplicant. (Another place said I had to start wpa_supplicant with the -u flag)
<tanonym> I have enabled wpa_supplicant and installed connman with Enlightenment 21.7. Wired and USB tether works flawlessly with connman. My wifi is enabled and recognized, but scanning wifi in the GUI doesn't work and the connmanctl scan wifi returns a technology not supported error.

2017-05-21

<mellowmaroon> For non-graphical setups, I think more people use wpa_supplicant, and that's included
<mellowmaroon> I prefer wpa_supplicant, but I don't like fighting GNOME/KDE
<mellowmaroon> NetworkManager doesn't use wpa_supplicant behind the scenes, does it?
<MichaelRaskin> I actually always use plain wpa_supplicant just because its config is versionable
<mdash> On the installer I ended up running wpa_supplicant by hand

2017-05-20

<grw> in wpa_supplicant package, wpa_supplicant.conf is only generated if wireless.networks is defined. but i think it should be if networks OR if userControlled = true

2017-05-16

<clever> wpa_supplicant does something with pcsclite, which has a python #!
<clever> makefu: wow, python actualy has a chance of being purged, only in use by git, wpa_supplicant, and zfs-user (grub shouldnt be using that)
<clever> wpa_supplicant

2017-04-29

<NixOS_GitHub> [nixpkgs] truh opened pull request #25325: wpa_supplicant_gui: fix icon resizing (master...wpa_gui-icon_resize) https://git.io/v9ClJ

2017-04-26

<disasm> MichaelRaskin: I was trying to do it from networking.wireless.networks but looking at nixpkgs it doesn't look like it supports it. I guess I'll just run wpa_supplicant manually.
<disasm> I'm stuck... How do I configure wpa_supplicant for wpa2 enterprise connections?

2017-04-14

<mtetreault> I am trying to enable connman but, wpa_supplicant complains as soon as I try to rebuild-switch. Is there any magic required to have wpa_supplicant working properly?.

2017-04-12

<cmacrae> stuff. For instance; wpa_supplicant's 'pskRaw' hex value for some WiFi networks, or my user account's hashedPassword (yep... I know it's hashed, but still). Just wondering what others do to approach this?

2017-04-10

<cmacrae`> I've opened the following issue for the wpa_supplicant problem I described above, in case anyone wants to track it :)
<cmacrae`> I can't imagine I'm the first one to run into this issue with wpa_supplicant on NixOS - but perhaps its due to my unfamiliarity with the configuration (only just started exploring :) ) - just really not sure how to remedy this

2017-04-05

<benley> DeaDSouL: ah yeah - if you have set networking.wireless.enable = true, you'll need to toggle that. Networkmanager conflicts with the thing that runs wpa_supplicant directly

2017-04-03

<bennofs> KABA: if it uses wpa_supplicant, then

2017-03-29

<crzyp3ck> goibhniu: thanks. I don't need network manager and such tools I just need wpa_supplicant and wpa_gui. what should I ass to my config file. please!

2017-03-27

<ocharles> having the fun dance of trying to get a machine to have internet access, but I don't have wpa_supplicant installed :')

2017-03-20

<glines> mmm.... I did notice the wpa_supplicant configuration in the nixos config
<globin> glines: I just use wpa_supplicant with a declarative config and for connecting to networks temporarily wpa_gui

2017-03-12

<devoid> … gonna take a second as wpa_supplicant is failing to handle my non-ascii ssid… gotta plug in

2017-03-11

<clever> samae: when i used wpa_supplicant, i just manualy copied a pre-existing config to /etc/wpa_supplicant.conf, and it just worked

2017-03-09

<sphalerite> wpa_passphrase ssid passphrase | wpa_supplicant -c/dev/stdin -iinterface
<Nazral> I have to turn on the wifi with wpa-supplicant first

2017-02-20

<ilyaigpetrov> I tried building master -- it fails on downloading vim8. Then I tried building 16.09 -- it fails on downloading wpa_supplicant

2017-02-02

<luigy> how does one get wpa_supplicant after a nixos-install without any internet connection? is there something I can do from the usb

2017-01-22

<fpletz> *wpa-supplicant

2017-01-01

<MichaelRaskin> Well, if I was trying to save reboots, I would mount the install media, chroot into it and export the closure of wpa_supplicant to import it on the installed system.
<MichaelRaskin> I think the install lacks wpa_supplicant package right now

2016-12-15

<clever> rardiol: and also stop wpa_supplicant before, and start it after
<jazzencat> I'm beginning to think that the issue is something about my router. connman, wicd and wpa_supplicant all don't work.
<jazzencat> So, looks like the hardware on my computer works fine with both connman and wpa_supplicant, but it doesn't like the router.
<jazzencat> The issue with wpa_supplicant is that it doesn't play with Enlightenment.
<clever> jazzencat: i havent used connman before, so all i can do is help setup bare wpa_supplicant
<jazzencat> This is following the ArchLinux WPA Supplicant wiki
<jazzencat> Okay, having a little difficulty connect with wpa_supplicant.
<jazzencat> Trying with wpa_supplicant and with boot.kernelPackages line.
<jazzencat> I haven't tried that yet. I'll try wpa_supplicant only. I need to comment out the connman line and enable network.wireless in configuration.nix, right?
<kmicu> jazzencat: did you try NetworkManager or only wpa_supplicant just to check if you can connect at all?
<sboo> Successfully initialized wpa_supplicant
<sboo> sudo wpa_supplicant -D nl80211,wext -i $MY_NETWORK -c ~/wpa_supplicant.conf`

2016-12-14

<kmicu> If wpa_supplicant runs then connman should work flawlessly now. :)
<kmicu> You could ‘sudo touch /etc/wpa_supplicant.conf’ and ‘sudo systemctl restart wpa_supplicant’.
<kmicu> (connman needs wpa_supplicant and there is/was a bug with missing /etc/wpa_supplicant.conf resulting in no wifi.)
<kmicu> jazzencat: what’s the output of ‘sudo systemctl status wpa_supplicant’?
<jazzencat> Does connman need wpa_supplicant.conf? I thought they were separate things. The manual says I can't have networkmanager and wireless (wpa_supplicant) active at the same time in configuration.nix
<clever> i havent done anything with connman, i just run raw wpa_supplicant

2016-12-05

<clever> exec wpa_supplicant -s -u -Dnl80211,wext -c /etc/wpa_supplicant.conf $ifaces
<anelson> does your systemd unit have the -u option in its call to wpa_supplicant?
<anelson> and I'm able to connect if I start wpa_supplicant manually
<clever> anelson: no idea what happened to wpa_supplicant, last i tried (a month ago) it just worked when i put a config file in /etc/wpa_supplicant.conf
<anelson> Failed to initialize wpa_supplicant
<anelson> my interface shows up in ifconfig, and I'm able to manually connect with wpa_supplicant, but the systemd unit that nixos sets up does not work