Bug#490063: [pkg-wpa-devel] Bug#490063: wpasupplicant: Doesn't work with WPA-NONE (ad-hoc)

2008-07-12 Thread Vedran Furač 
Kel Modderman wrote:

 On Thursday 10 July 2008 03:00:24 =?UTF-8?B?VmVkcmFuIEZ1cmHEjQ==?= wrote:
 Kel Modderman wrote:
 I tried to setup WPA in Ad-Hoc mode but failed. On the other hand in 
 windows
 this works fine which means that other peer is configured properly.
 http://lists.shmoo.com/pipermail/hostap/2008-July/018036.html
 Yes, I think I saw that. There's a 2.6.26-rc9 package on kernel
 buildserver so I only need recent git pull of the supplicant.
 
 You can try something from:
 http://sidux.net/kelmo/debian/pool/main/w/wpasupplicant/

Thank you for packaging. Unfortunately it still doesn't work. Is there any
way I can find out if there was a password mismatch as I don't understand
anything from the log file.
And btw. driver for b43 from 2.6.26 is acting strangely, I get this
messages at rate of around 20 per second:

wlan1: Configured IBSS beacon template
phy0: Adding new IBSS station 00:0e:2e:5c:c7:75 (dev=wlan1)


Regards,

Vedran



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#490063: wpasupplicant: Doesn't work with WPA-NONE (ad-hoc)

2008-07-09 Thread Vedran Furač 
Package: wpasupplicant
Version: 0.6.3-2
Severity: important

I tried to setup WPA in Ad-Hoc mode but failed. On the other hand in windows
this works fine which means that other peer is configured properly.

Driver: b43 (broadcom)
Configuration:

network={
   ssid=home_vedranf
   mode=1
   proto=WPA
   key_mgmt=WPA-NONE
   pairwise=NONE
   group=TKIP
   psk=test1234
   frequency=2412
   id_str=wlan-home
}

Log:

1215610714.229201: Initializing interface 'wlan1' conf 
'/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' 
bridge 'N/A'
1215610714.229338: Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' 
- '/etc/wpa_supplicant/wpa_supplicant.conf'
1215610714.229359: Reading configuration file 
'/etc/wpa_supplicant/wpa_supplicant.conf'
1215610714.229449: ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=netdev'
1215610714.229489: fast_reauth=1
1215610714.229503: ap_scan=2
1215610714.257150: Priority group 1
1215610714.257168:id=1 ssid='eduroam'
1215610714.257180: Priority group 0
1215610714.257190:id=0 ssid='home_vedranf'
1215610714.257201: Initializing interface (2) 'wlan1'
1215610715.946561: Interface wlan1 set UP - waiting a second for the driver to 
complete initialization
1215610718.781232: SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
1215610718.781296:   capabilities: key_mgmt 0xf enc 0xf
1215610718.849964: WEXT: Operstate: linkmode=1, operstate=5
1215610718.869479: Own MAC address: 00:1a:73:f8:a2:6e
1215610718.869493: wpa_driver_wext_set_wpa
1215610718.869503: wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 
key_len=0
1215610718.869516: wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 
key_len=0
1215610718.869525: wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 
key_len=0
1215610718.869533: wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 
key_len=0
1215610718.869541: wpa_driver_wext_set_countermeasures
1215610718.869548: wpa_driver_wext_set_drop_unencrypted
1215610718.869555: RSN: flushing PMKID list in the driver
1215610718.869578: Setting scan request: 0 sec 10 usec
1215610718.871877: EAPOL: SUPP_PAE entering state DISCONNECTED
1215610718.871897: EAPOL: KEY_RX entering state NO_KEY_RECEIVE
1215610718.871903: EAPOL: SUPP_BE entering state INITIALIZE
1215610718.871911: EAP: EAP entering state DISABLED
1215610718.872490: ctrl_interface_group=105 (from group name 'netdev')
1215610718.872571: Added interface wlan1
1215610718.872579: Daemonize..
1215610718.873026: CTRL_IFACE - wlan1 - wait for monitor to attach
1215610718.954613: CTRL_IFACE monitor attached - hexdump(len=21): 2f 74 6d 70 
2f 77 70 61 5f 63 74 72 6c 5f 33 36 37 30 2d 30 00
1215610718.954744: Ignore event for foreign ifindex 3
1215610718.954771: RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
1215610718.954796: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan1' added
1215610718.954827: RTM_NEWLINK: operstate=0 ifi_flags=0x11043 
([UP][RUNNING][LOWER_UP])
1215610718.954841: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan1' added
1215610718.954855: Ignore event for foreign ifindex 3
1215610718.954868: RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
1215610718.954880: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan1' added
1215610718.954894: RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
1215610718.954905: Wireless event: cmd=0x8b06 len=12
1215610718.954919: Ignore event for foreign ifindex 3
1215610718.954931: RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
1215610718.954943: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan1' added
1215610718.954957: RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
1215610718.954969: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan1' added
1215610718.970494: State: DISCONNECTED - SCANNING
1215610718.970564: Trying to associate with SSID 'home_vedranf'
1215610718.970587: CTRL_IFACE monitor send - hexdump(len=21): 2f 74 6d 70 2f 77 
70 61 5f 63 74 72 6c 5f 33 36 37 30 2d 30 00
1215610718.970657: Cancelling scan request
1215610718.970678: WPA: clearing own WPA/RSN IE
1215610718.970692: Automatic auth_alg selection: 0x1
1215610718.970722: WPA: No WPA/RSN IE available from association info
1215610718.970734: WPA: Set cipher suites based on configuration
1215610718.970744: WPA: Selected cipher suites: group 8 pairwise 1 key_mgmt 16 
proto 1
1215610718.970760: WPA: clearing AP WPA IE
1215610718.970771: WPA: clearing AP RSN IE
1215610718.970782: WPA: using GTK TKIP
1215610718.970794: WPA: using PTK NONE
1215610718.970806: WPA: using KEY_MGMT WPA-NONE
1215610718.970818: WPA: not using MGMT group cipher
1215610718.970886: 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 00 01 00 00 50 f2 00
1215610718.970912: No keys have been configured - skip key clearing
1215610718.970927: wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 
key_len=32
1215610718.970959: wpa_driver_wext_set_drop_unencrypted
1215610718.970975: State: SCANNING -

Bug#490063: [pkg-wpa-devel] Bug#490063: wpasupplicant: Doesn't work with WPA-NONE (ad-hoc)

2008-07-09 Thread Kel Modderman 
On Thursday 10 July 2008 01:11:41 Vedran =?UTF-8?Q?Fura=C4=8D?= wrote:
 Package: wpasupplicant
 Version: 0.6.3-2
 Severity: important

Why is every problem with wpasupplicant Severity: important ... ;-)

 
 I tried to setup WPA in Ad-Hoc mode but failed. On the other hand in windows
 this works fine which means that other peer is configured properly.

http://lists.shmoo.com/pipermail/hostap/2008-July/018036.html

Thanks, Kel.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#490063: [pkg-wpa-devel] Bug#490063: wpasupplicant: Doesn't work with WPA-NONE (ad-hoc)

2008-07-09 Thread Vedran Furač 
Kel Modderman wrote:

 On Thursday 10 July 2008 01:11:41 Vedran =?UTF-8?Q?Fura=C4=8D?= wrote:
 Package: wpasupplicant
 Version: 0.6.3-2
 Severity: important
 
 Why is every problem with wpasupplicant Severity: important ... ;-)

Yesterday I tried to setup WEP encryption but failed (reported #489948)
and today tried WPA and also failed (reported this). So I assumed that
wpa_supplicant is completely broken for ad-hoc mode and I find this
important. If you disagree then please change the severity.
Btw. I usualy report this kind of bugs directly to the upstream but their
bugzilla requires me to get an account and I don't want to register.

 I tried to setup WPA in Ad-Hoc mode but failed. On the other hand in windows
 this works fine which means that other peer is configured properly.
 
 http://lists.shmoo.com/pipermail/hostap/2008-July/018036.html

Yes, I think I saw that. There's a 2.6.26-rc9 package on kernel
buildserver so I only need recent git pull of the supplicant.

Regards,

Vedran





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#490063: [pkg-wpa-devel] Bug#490063: wpasupplicant: Doesn't work with WPA-NONE (ad-hoc)

2008-07-09 Thread Kel Modderman 
On Thursday 10 July 2008 03:00:24 =?UTF-8?B?VmVkcmFuIEZ1cmHEjQ==?= wrote:
 Kel Modderman wrote:
 
  On Thursday 10 July 2008 01:11:41 Vedran =?UTF-8?Q?Fura=C4=8D?= wrote:
  Package: wpasupplicant
  Version: 0.6.3-2
  Severity: important
  
  Why is every problem with wpasupplicant Severity: important ... ;-)
 
 Yesterday I tried to setup WEP encryption but failed (reported #489948)
 and today tried WPA and also failed (reported this). So I assumed that
 wpa_supplicant is completely broken for ad-hoc mode and I find this
 important. If you disagree then please change the severity.
 Btw. I usualy report this kind of bugs directly to the upstream but their
 bugzilla requires me to get an account and I don't want to register.

I understand, was just making a cheeky remark based on the severity of last
dozen or so bug reports.

 
  I tried to setup WPA in Ad-Hoc mode but failed. On the other hand in 
  windows
  this works fine which means that other peer is configured properly.
  
  http://lists.shmoo.com/pipermail/hostap/2008-July/018036.html
 
 Yes, I think I saw that. There's a 2.6.26-rc9 package on kernel
 buildserver so I only need recent git pull of the supplicant.

You can try something from:
http://sidux.net/kelmo/debian/pool/main/w/wpasupplicant/

Or wait for next upload I guess.

Thanks, Kel.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]