Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)

2011-03-17 Thread Radek Polak
On Tuesday 08 March 2011 22:29:22 Alfa21 wrote:

 2011-03-05@17:14 Alfa21
 
  2011-03-05@12:42 Radek Polak
  
* unable to connect wifi wpa2-psk
   
   Was is working in some older versions? It can be bug either in
   wpa_supplicatant or in qmoko wifi plugin that creates configuration for
   wpa_supplicant. Does it work when you setup wpa_supplicant from command
   line? I am trying to connect WPA2-psk here and it does not work too :(
  
  previously I had v31 and it was ok, but only on the first attempt and
  then I needed to reboot (rebooted also because wifi didn't stop and
  battery drain empty in few hours) the blue led in v31 did never turn on
  while connected.
  before v31 it was all ok... IIRC
 
 hi,
 I tried to manually configure the wifi link:
 as you can read below, seems to be something different with the wpa driver
 in v33...

Hmm i just tested wpa2-psk here at work and it works (only the first connect 
after reboot). But it can be of course different AP. You could try to enable 
Networking category in Settings-Logging and send me full log. Or you could 
try to replace wpa_supplicant with package from lenny. But I am not wifi expert 
so cant promise anything.

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)

2011-03-17 Thread Alfa21 mobile

On Wednesday, March 16, 2011 13:17:56, Radek Polak wrote:
 On Tuesday 08 March 2011 22:29:22 Alfa21 wrote:
 
  2011-03-05@17:14 Alfa21
  
   2011-03-05@12:42 Radek Polak
   
 * unable to connect wifi wpa2-psk

Was is working in some older versions? It can be bug either in
wpa_supplicatant or in qmoko wifi plugin that creates configuration for
wpa_supplicant. Does it work when you setup wpa_supplicant from command
line? I am trying to connect WPA2-psk here and it does not work too :(
   
   previously I had v31 and it was ok, but only on the first attempt and
   then I needed to reboot (rebooted also because wifi didn't stop and
   battery drain empty in few hours) the blue led in v31 did never turn on
   while connected.
   before v31 it was all ok... IIRC
  
  hi,
  I tried to manually configure the wifi link:
  as you can read below, seems to be something different with the wpa driver
  in v33...
 
 Hmm i just tested wpa2-psk here at work and it works (only the first connect 
 after reboot). But it can be of course different AP. You could try to enable 
 Networking category in Settings-Logging and send me full log. Or you could 
 try to replace wpa_supplicant with package from lenny. But I am not wifi 
 expert 
 so cant promise anything.
 
 Regards
 
 Radek
 

hi radek, i'm sorry for the silence.
i found the solution about this topic:
1) qtmoko doesn't kill wpa-supplicant closing wifi the first good time, this is 
bad!
2) because of previous point i messed too much and missconfigured my ap.. so i 
tried with wrong settings, ignore me: current supplicant is ok!
3) remains the problem of battery discharge when you disconnect from wifi:maybe 
interface doesn't go to sleep?btw i can force this by script (wifi off)

regards!
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)

2011-03-17 Thread Radek Polak
Alfa21 mobile wrote:

 hi radek, i'm sorry for the silence.
 i found the solution about this topic:
 1) qtmoko doesn't kill wpa-supplicant closing wifi the first good time,
 this is bad!

I think i can add this to the wifi script, it should be quite easy.

 2) because of previous point i messed too much and
 missconfigured my ap.. so i tried with wrong settings, ignore me: current
 supplicant is ok!

Great!

 3) remains the problem of battery discharge when you
 disconnect from wifi:maybe interface doesn't go to sleep?btw i can force
 this by script (wifi off)


I think we can add this to wifi script as well. I will do it tomorrow at work 
where i can test it.

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)

2011-03-17 Thread Alfa21 mobile

 
  3) remains the problem of battery discharge when you
  disconnect from wifi:maybe interface doesn't go to sleep?btw i can force
  this by script (wifi off)
 
 
 I think we can add this to wifi script as well. I will do it tomorrow at work 
 where i can test it.
 
 Regards
 
 Radek
 

no, beware! if you turn off wifi in that way, then the line in internet gui 
tells no wifi interfaces available! it's too low level in that way, imo.
i would prefer a way which put the interface in its initial state but keeps it 
available and not removed.
i've to check but maybe killing supplicant is just enough... i'll verify and 
report you about that.

regards
ps: now i'm on wifi with qtmoko email client, from a pub's hotspot ;)
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)

2011-03-17 Thread zyth

Hi,

I can confirm that there is no problem with wifi wpa-psk/wpa2-psk
in aes encryption mode (qtmoko v.33).

But there is other annoying thing: fbreader canot be started from QX,
if someone knows a solution please tell me or fix it (radek).


On Wed, 16 Mar 2011 13:17:56 +0100, Radek Polak wrote:

On Tuesday 08 March 2011 22:29:22 Alfa21 wrote:


2011-03-05@17:14 Alfa21

 2011-03-05@12:42 Radek Polak

   * unable to connect wifi wpa2-psk
 
  Was is working in some older versions? It can be bug either in
  wpa_supplicatant or in qmoko wifi plugin that creates 
configuration for
  wpa_supplicant. Does it work when you setup wpa_supplicant from 
command
  line? I am trying to connect WPA2-psk here and it does not work 
too :(


 previously I had v31 and it was ok, but only on the first attempt 
and
 then I needed to reboot (rebooted also because wifi didn't stop 
and
 battery drain empty in few hours) the blue led in v31 did never 
turn on

 while connected.
 before v31 it was all ok... IIRC

hi,
I tried to manually configure the wifi link:
as you can read below, seems to be something different with the wpa 
driver

in v33...


Hmm i just tested wpa2-psk here at work and it works (only the first 
connect
after reboot). But it can be of course different AP. You could try to 
enable
Networking category in Settings-Logging and send me full log. Or you 
could

try to replace wpa_supplicant with package from lenny. But I am not
wifi expert
so cant promise anything.

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


[qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)

2011-03-08 Thread Alfa21
2011-03-05@17:14 Alfa21

 2011-03-05@12:42 Radek Polak
 
   * unable to connect wifi wpa2-psk  
  
  Was is working in some older versions? It can be bug either in 
  wpa_supplicatant or in qmoko wifi plugin that creates configuration for 
  wpa_supplicant. Does it work when you setup wpa_supplicant from command 
  line? 
  I am trying to connect WPA2-psk here and it does not work too :(  
 
 previously I had v31 and it was ok, but only on the first attempt and then I 
 needed to reboot
 (rebooted also because wifi didn't stop and battery drain empty in few hours)
 the blue led in v31 did never turn on while connected.
 before v31 it was all ok... IIRC


hi,
I tried to manually configure the wifi link:
as you can read below, seems to be something different with the wpa driver in 
v33...

Initializing interface 'eth0' conf '/etc/wpa_supplicant/test.conf' driver 
'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/test.conf' - 
'/etc/wpa_supplicant/test.conf'
Reading configuration file '/etc/wpa_supplicant/test.conf'
ctrl_interface='/var/lib/wpa_supplicant'
ctrl_interface_group='0'
eapol_version=1
fast_reauth=1
ap_scan=1
Priority group 0
   id=0 ssid='A21_net'
Initializing interface (2) 'eth0'
Interface eth0 set UP - waiting a second for the driver to complete 
initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=13 enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3 flags 0x0
ioctl[SIOCSIWESSID]: Invalid argument
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:XX:XX:XX:XX:XX
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 10 usec


-- 
ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR 
IMPLIED.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community