Tag Info

Hot answers tagged

4

Preferred DHCP addresses are usually configured on the DHCP server side. You will need to add an entry in your DHCP server's address table for your device's MAC address and assign it to an IP address. DHCP servers can vary. If this is a small network your DHCP server may be your router or gateway. The address can fall in the range of DHCP addresses but it ...


2

The errors wpa_supplicant produces are not necessarily related to your wpa_cli connection problem. The trouble here is that wpa_cli is unable to establish connection with wpa_supplicant - unable to open the control socket. This can have several causes: user running wpa_cli is unable to access the socket given e.g. in wpa_supplicant.conf: ...


2

This is probably your dhcp client blocking until it the interface has an address. The exact answer will depend on what init system you use and what dhcp client you use. For dhcpcd, for example, you want to make sure the init script that launches it is called with the -b flag (background immediately), and if it has the -w flag (wait), to erase it. One ...


2

Probably what is happening here is that some other process owns the wireless chip inside your computer, so NetworkManager isn't allowed to do anything. In this case, that process would be wpa_supplicant or whatever is calling wpa_supplicant (and acting on the information in /etc/network/interfaces). Instead of randomly installing things, you should stop and ...


2

The key to solving problems such as this is knowing how to ask the question. I searched Google looking for "how to access panera bread wifi" and turned up this gem. Auto login to open Wifi This article had several scripts that could be used to facilitate the auto logging in. I've opted to include the example for Panera Bread which leverages Python's ...


2

No, you cannot replace the password by a hash. It doesn't matter what the protocol is. The client needs to know the password, and then either it sends the password to the server, or it sends some data that proves that the client knows the password. The server can be content to know the hash of the real password, because when it receives a candidate ...


1

Just Download a Live-Distro of your choice (with wpa_supplicant) with the same arch (32/64 bit) you'll choose for gentoo later, too Create a bootable USB-Stick from it Boot from the USB-Stick Most of the upcomping steps require root privileges, so you could do a su in your Live-Distro and go on as root. Create your partitions (/boot,/home/,/) e.g. with ...


1

Looks like you are missing the wpa keyword in your hostname.iwn0. You have: dhcp nwid Livebox-5dxx wpakey xxxxxxxxxxxxxxxxxxxxxxxxxx I think it should be: dhcp nwid Livebox-5dxx wpa wpakey xxxxxxxxxxxxxxxxxxxxxxxxxx It's normal for it to report the wpakey as 0xabcdef..... ifconfig allows you to specify a passphrase as a convenience to you. It ...


1

Your interface name is eth1 and not wlan0. Replace wlan0 in all commands with eth1, and it should work.


1

If your system is not reporting a device wlan0 as available then the Linux kernel was unsuccessful in detecting your hardware and associating a driver to it. I would start by looking in the dmesg output for any messaging related to the Broadcom device. If it's being reported there in any way then the appropriate driver is either not present within the ...


1

You can't. Easiest solution for you would be for your AP to ban the MAC address of your client. That, or just stop trying to connect to every open BSS network out there.


1

Depending on how the authentication is implemented, you may be able to send a HTTP request to gain access. This depends on numerous aspects of the particular implementation though. Keep in mind, these types of authentication are put into place to keep autonomous systems out while allowing only browsers to have access, which is exactly what you are trying ...


1

It is little known feature, but Conky can be run in console mode with its variables describing network: http://conky.sourceforge.net/variables.html You could edit any conkyrc and use output_to_x and output_to_console variables to have conky render text in console. Also you could try wifi-menu (for network selection and control) and wawemon (nice wifi ...


1

I know thats not 'the Anwser', and also a bit late - But its to large for a comment. Maybe it helps... My Configuration was not wrong, it just took to long to connect and caused a timeout, setting explicit values speeded it up and the autentication was finished in time. Try to do so with eapol_flags and eap, try disabling eap_workaround or fast_reauth. ...


1

To get log into file for multiple WLAN interface you would have to run one wpa_supplicant instance per WLAN interface with -f and -d options. This way you'll get one log file per interface. I don't think, that wpa_supplicant would automatically change its verbosity level after connection. You could submit such a feature request. Another way to troubleshoot ...


1

You are confusing kernel drivers and user-space drivers. In your case, you may certainly use WEXT, but also nl80211 (I think). WEXT (or WE= Wireless Extensions) are the modification introduced to the Linux kernel in 1997 by Jean Tourrhiles. According to this Web page written by Tourrhiles himself, The Wireless Extension (WE) is a generic API allowing ...


1

Reading the pacman man page, it looks to me like you could do this: pacman --root /mnt -S wpa_supplicant while you have the "live Arch" CD booted, and the "/" partitioned mounted on /mnt. That might be a little more complicated if you have a separate /usr partition. You'll probably have to fix up the /etc/wpa_supplicant/wpa_supplicant.conf file after ...


1

Did you setup your passphrase with wpa_passphrase? e.g %> wpa_passphrase SSID passphrase network={ ssid="SSID" #psk="passphrase" psk=28964ba6ea8b8f3a0db1c4414b327da253d0af5d4f4adccec0f8abf5b05b10f8 } Otherwise wpa_supplicant -B -i [wireless device] -c /etc/wpa_supplicant/cli.conf won't work at all


1

This kind of problem is better divided into independent parts. In this case, circumventing ifupdown completely and doing all the steps manually - that is: run wpa_supplicant with an appropriate config file once connection is established, running dhcp client, To check how ifupdown runs wpa_supplicant - it has to pass it some sort of configuration in a ...


1

This is the order of things I'd try when debugging a flaky wireless device. Does a reboot resolve the issue? Try unloading the kernel drivers related to the wireless device. Something to the effect of the following: $ lsmod | grep iw iwlagn 209751 0 iwlcore 195714 1 iwlagn mac80211 229095 2 iwlagn,iwlcore ...



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