[Bug 102385] Re: netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point.

2007-09-17 Thread Nanley Chery
** Changed in: wpasupplicant (Ubuntu)
   Status: Incomplete = Confirmed

-- 
netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to 
associate with access point.
https://bugs.launchpad.net/bugs/102385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102385] Re: netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point.

2007-06-23 Thread tknieper
I gave current ndiswrapper-utils-1.9 and wpasupplicant packages from
gutsy a try but had no luck. Still the same issue, pairing needs endless
tries till it succeeds.

See also my previous comment at the dup:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/108013/comments/9

Regards,
Tobias

-- 
netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to 
associate with access point.
https://bugs.launchpad.net/bugs/102385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102385] Re: netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point.

2007-04-30 Thread Reinhard Tartler
according to http://thread.gmane.org/gmane.linux.drivers.hostap/15839,
it should help if you guys restrict usage of TKIP (wpa1 only). could you
please read the linked thread retry again?

-- 
netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to 
associate with access point.
https://bugs.launchpad.net/bugs/102385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102385] Re: netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point.

2007-04-30 Thread Reinhard Tartler
08:51:16  crimsun siretart: I do.
08:51:21  crimsun Do you need something tested?
08:51:57  siretart crimsun: it's about bug #108013
08:52:23  siretart I can't really believe it, and I think I've found 
something relevant on the upstream mailing list
08:52:26  crimsun wpa_supplicant in 7.04 definitely works with ndiswrapper.
08:52:46  crimsun I've got an unfortunate bcm4311
08:53:07  siretart ok, then the upstream post ist most probably correct

-- 
netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to 
associate with access point.
https://bugs.launchpad.net/bugs/102385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102385] Re: netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point.

2007-04-26 Thread Damien Challet
I confirm this bug on Feisty final. Same story (OK with Edgy, does not
work with Feisty), does not associate with WPA.

-- 
netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to 
associate with access point.
https://bugs.launchpad.net/bugs/102385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102385] Re: netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point.

2007-04-18 Thread PearzooPeter
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 
'ndiswrapper' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' - '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=7):
 50 45 41 52 5a 4f 4f  PEARZOO 
proto: 0x1
key_mgmt: 0x2
pairwise: 0x8
group: 0x8
PSK (ASCII passphrase) - hexdump_ascii(len=21): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='PEARZOO'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=21 WE(source)=18 enc_capa=0x5
  capabilities: key_mgmt 0x5 enc 0x7
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:0f:b5:04:a4:55
Driver does not support WPA.
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
Setting scan request: 0 sec 10 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED - SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed 
up initial association
Received 970 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 0
0: 00:18:4d:c7:1f:ae ssid='PEARZOO' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   selected based on WPA IE
Trying to associate with 00:18:4d:c7:1f:ae (SSID='PEARZOO' freq=2452 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 
00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 
02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING - ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0-0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:18:4d:c7:1f:ae into blacklist
State: ASSOCIATING - DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0-0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED - SCANNING
Starting AP scan (broadcast SSID)
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: SCANNING - DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0-0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Failed to disable WPA in the driver.
No keys have been configured - skip key clearing
WEXT: Operstate: linkmode=0, operstate=6
Removed BSSID 00:18:4d:c7:1f:ae from blacklist (clear)
Cancelling scan request


** Attachment added: wpa_supplicant.conf
   http://librarian.launchpad.net/7342331/wpa_supplicant.conf

-- 
netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to 
associate with access point.
https://bugs.launchpad.net/bugs/102385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102385] Re: netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point.

2007-04-18 Thread PearzooPeter
I hope this helps, is there any more info that you require?

-- 
netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to 
associate with access point.
https://bugs.launchpad.net/bugs/102385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 102385] Re: netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to associate with access point.

2007-04-05 Thread Reinhard Tartler
please attach a debug log (use parameters -dd), and attach your
wpa_supplicant configuration file to this bug.

** Changed in: wpasupplicant (Ubuntu)
   Status: Unconfirmed = Needs Info

-- 
netgear wg311v2 (acx chipset) using ndiswrapper 1.9 and wpa supllicant fails to 
associate with access point.
https://bugs.launchpad.net/bugs/102385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs