New answers tagged


So after a lot of digging, I found that the issue was because of the kernel's rtlwifi driver. To me, it looks like the rtl8192cu driver was suppose to be responsible for handling missed beacons, by calling the function ieee80211_beacon_loss, but that call is nowhere to be found. I removed support for IEEE80211_HW_BEACON_FILTER in the rtlwifi driver and the ...


Just found it on the official homepage:


To connect through wpa_cli open the terminal and type the following command: wpa_cli scan scan_results To create a network type: add_network the output will be 0or 1 ..(remember the output it will be used next time) To connect type the follwing command: set_network 0 ssid "SSID_here" set_network 0 psk "Passphrase_here" dhclient wlan0


I'm embarrassed to say the solution was to kill the already running wpa_supplicant process. The -B argument causes the program to fork into the background, and trying to run it again will fail as long as it is already running. I'm still not sure why it prints that first error message, but it connects to wireless networks without issue.


We also have a similar situation here with the FON network in Nós (old ZON) operator. In the past I tried this procedure, nowadays they have randomised the initial URL to try to prevent this, I am planning do some tests in a near future. BT and here our provider use captive portals to authenticate users. If I am not wrong, my own credentials work in BT in ...


Solution I installed network-manager and network-manager-gnome and removed my wlan1 card from /etc/network/interfaces. The card remained stably connected for over 20 hours and only disconnected when I shut down the raspberry pi. The WPA Gui says "cannot get status from wpa_supplicant" but the card works anyway. Looks like nm-applet has problems with ...


It APPEARS that the ar6k driver has flaws. I'm surprised about this being an Atheros product. Check out the hardware notes/forums for your particular system regarding this driver. The shell command and .conf file didn't appear to have any errors. Can you connect to a non-encrypted network?


Process substitution <(…) creates a pipe, uses /dev/fd to give a path that's equivalent to the file descriptor where the pipe is, and passes the file name as an argument to the program. Here the program is sudo, and it passes that argument (which is just a string, as far as it's concerned) to wpa_supplicant, which treats it as a file name. The problem is ...

Top 50 recent answers are included