Hot answers tagged

4

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 ...


3

Quoting the ArchLinux wiki: Note: Because of the process substitution, you cannot run this command with sudo - you will need a root shell. You should be able to use su -c under sudo like so: $ sudo su -c 'wpa_supplicant -D nl80211,wext -i wlp4s0 -c \ <(wpa_passphrase "some ssid" "password")'


2

The cheap Realtek wifi firmware, linux kernel drivers and the hardware itself are terribly buggy. People in the ARM community have been working around the clock to try to mitigate some of the problems, back porting old versions of realtek kernel modules and old versions of hostapd, and often old versions of firmware too. One of the drivers backported for ...


2

You can generate the NtPasswordHash (aka NTLM password hash) yourself as follows: echo -n plaintext_password_here | iconv -t utf16le | openssl md4 Prefix it with "hash:" in the wpa_supplicant.conf file, i.e. password=hash:6602f435f01b9173889a8d3b9bdcfd0b


2

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?


2

Create a new file /etc/modprobe.d/rt2800usb.conf with the following line : options rt2800usb nohwcrypt=1 Reboot Or blacklist the defaut drivers and use the nl80211driver to connect through wpa_supplicant: nano /etc/modprobe.d/blacklist.conf add the following lines: blacklist rt2800usb blacklist rt2x00lib blacklist rt2x00usb Connect through the ...


2

I've not found official documentation about the /etc/network/interfaces config. You can find the documentation at /usr/share/doc/wpasupplicant/README.Debian.gz. Under Chapter 4: Troubleshooting there's a section titled Hidden ssids: In order to be able to associate to hidden ssids, please try to set the option 'ap_scan=1' in the global section, and ...


1

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 ...


1

According to wiki.archlinux You can use one connection manager because: you should not run two daemons simultaneously netctl is installed by default, i think you are using a GUI like Network-manager. Remove netctl and Network-manager Reinstall Network-Manager Try to connect through wpa_supplicant


1

I ended up solving this problem by not connecting to the internet connection directly, but through connecting to my other machine which is already connected to wifi, thus eliminating the need to enter a username/password on the client. I did this by following the steps here, except for Linux Mint 17.3 KDE. To do so, I used these basic steps: Connect ...


1

I have 2 wireless access points too. Here's what I do: Have systemd start wpa_supplicant at boot. Put both access points in /etc/wpa_supplicant/wpa_supplicant.conf. That looks something like: network={ ssid="Jan Vermeer of Delft" psk="SOmeThing" priority=3 } network={ ssid="Pieter Brueghel the Younger" ...


1

The solution is to install an NTP client, and configure a script on the directories that have scripts to run after the interfaces go up. You would want to execute a script after the interface goes up. If In Debian do: $sudo apt-get install ntpdate The create the following script with vi sudo vi /etc/network/if-up.d/ntpdate and place in the vi file ...


1

After messing around for hours I managed to cook something decent up using zenity and some sudoers changes. I'll give a step by step how I did it all, in case someone else is caught in the ugly situation of being on a linux distro that only has obsolete wireless networking software (like wireless-tools) without any easy way to get a known GUI like wicd... ...


1

Apparently these networks with web-based auth rely on MAC based access control post-authentication, so you can simply authenticate on a different device while spoofing your Pi's MAC address, and then your Pi should be able to get on the network. Got this tip from http://frankiejarrett.com/how-to-connect-apple-tv-to-a-hotel-wi-fi-network/



Only top voted, non community-wiki answers of a minimum length are eligible