Hi,
On Sunday 08 January 2006 22:48, Dan Williams wrote:
*) Your driver probably doesn't support WPA quite enough; you'll need a
driver that does WEXT-18 or higher. This means that it needs to set
the enc_capa bits on return from the SIOCGIWRANGE call, which only
hostap seems to do right
On Mon, 2006-01-09 at 10:58 +0100, Nikolaus Filus wrote:
Hi,
On Sunday 08 January 2006 22:48, Dan Williams wrote:
*) Your driver probably doesn't support WPA quite enough; you'll need a
driver that does WEXT-18 or higher. This means that it needs to set
the enc_capa bits on return
On Mon, 2006-01-09 at 10:55 -0500, Robert Love wrote:
On Sun, 2006-01-08 at 16:48 -0500, Dan Williams wrote:
*) Your driver probably doesn't support WPA quite enough; you'll need a
driver that does WEXT-18 or higher. This means that it needs to set the
enc_capa bits on return from the
On Mon, 2006-01-09 at 11:11 -0500, Dan Williams wrote:
Just to use WPA. All cards should support WEP already since you don't
need fancy calls to do that... Unless wpa_supplicant is trying to be
clever.
Seems to be. SIOCSIWAUTH not being supported shuts the whole process
down. This is an
On Mon, 2006-01-09 at 11:16 -0500, Robert Love wrote:
Seems to be. SIOCSIWAUTH not being supported shuts the whole process
down. This is an Atheros.
Alright, got it working. Nice!
I still see a boatload of SIOCSIWAUTH Operation not supported errors.
But, whatever.
Is 0.4.7 + your patch
On Mon, 2006-01-09 at 11:31 -0500, Robert Love wrote:
On Mon, 2006-01-09 at 11:16 -0500, Robert Love wrote:
Seems to be. SIOCSIWAUTH not being supported shuts the whole process
down. This is an Atheros.
Alright, got it working. Nice!
I still see a boatload of SIOCSIWAUTH Operation
On Mon, 2006-01-09 at 11:46 -0500, Dan Williams wrote:
I think 0.4.7 is OK, I'm using HEAD but looking at the changelog there's
not much that should affect functionality since before Christmas at
least. I think at the very least we should make sure 0.4.7 works
correctly for us, and patch it
On Mon, 2006-01-09 at 12:02 -0500, Robert Love wrote:
On Mon, 2006-01-09 at 11:46 -0500, Dan Williams wrote:
I think 0.4.7 is OK, I'm using HEAD but looking at the changelog there's
not much that should affect functionality since before Christmas at
least. I think at the very least we
On Mon, 2006-01-09 at 10:55 -0500, Robert Love wrote:
On Sun, 2006-01-08 at 16:48 -0500, Dan Williams wrote:
*) Your driver probably doesn't support WPA quite enough; you'll need a
driver that does WEXT-18 or higher. This means that it needs to set the
enc_capa bits on return from the
On Mon, 2006-01-09 at 12:18 -0500, Dan Williams wrote:
Note that while wpa_supplicant supports using driver-specific methods
for WPA and other settings, we want to push all drivers towards
conforming to the WEXT spec on this one. That means support for
SIOCSIWAUTH and SIOCSIWENCODEEXT. We
Yesterday, I built 1.710 which did not use the bogus AP_SCAN ctrl
command and it worked fine. Today, I build 1.721 and the bug log showed
the following because the invalid AP_SCAN ctrl command had been added to
the NM code.
Jan 9 12:45:43 localhost NetworkManager: information SUP: sending
I've been playing around with CCMP (AES). I've found that if I first
associate with TKIP, and
then /system/networking/wireless/networks/ssid/we_cipher to 8 in
gconf, NetworkManager then tells wpa_supplicant to use CCMP. It then
goes on to authenticate and pick up an IP address. Although
On Mon, 2006-01-09 at 14:38 -0500, Robert Love wrote:
On Mon, 2006-01-09 at 14:27 -0500, Bill Moss wrote:
3. NM is now connecting at home with broadcast essid and at work with
hidden essid.
Was it not working before?
It will fail out and refuse to connect if AP_SCAN can't be set.
On Tue, 2006-01-10 at 00:08 +, James Ettle wrote:
I've been playing around with CCMP (AES). I've found that if I first
associate with TKIP, and
then /system/networking/wireless/networks/ssid/we_cipher to 8 in
gconf, NetworkManager then tells wpa_supplicant to use CCMP. It then
goes on to
On Mon, 2006-01-09 at 12:27 -0500, Robert Love wrote:
On Mon, 2006-01-09 at 12:18 -0500, Dan Williams wrote:
Note that while wpa_supplicant supports using driver-specific methods
for WPA and other settings, we want to push all drivers towards
conforming to the WEXT spec on this one. That
On Mon, 2006-01-09 at 15:19 -0500, Bill Moss wrote:
Yesterday, I built 1.710 which did not use the bogus AP_SCAN ctrl
command and it worked fine. Today, I build 1.721 and the bug log showed
the following because the invalid AP_SCAN ctrl command had been added to
the NM code.
Jan 9 12:45:43
1. Patched wpa_supplicant-0.5.0 using Dan's patch at
http://people.redhat.com/dcbw/wpa_supplicant-ctrl-iface-ap-scan.patch
and the .config file
CONFIG_WIRELESS_EXTENSION=y
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_WIRED=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
17 matches
Mail list logo
