wifi.tcz

[coreplayer2]

Am not sure you this feedback was ever found from v0.2  from here http://forum.tinycorelinux.net/index.php?topic=10283.msg55735#msg55735

I still have these same two questions

why the need for entering the password twice when attempting to connect ?  there is a need to confirm the password in the event of a misspelling etc when setting the password at the Access Point, but from the client???   seems to have only one possible purpose to ensure the correct password is save in database, but I question if that's really necessary since the password may not be correct even if the spelling is.  this only delays the initial attempt to connect..

and

wifi.sh  detects a connection even when there isn't one, ie a wifi device is found and identified as wlan0 however the device is not associated with any AP and is not assigned an ip address.  yet wifi.sh reports already connected and queries to disconnect and rescan.

[roberts]

I have found on some wifi devices that trying to connect with a bad password will hang the device.
The only recovery is a hard boot. So entering password twice to verify minimizes the case for a poweroff recovery. Passwords are stored in the wifi.db. It is not like it something that needs to be done upon every boot or every access. Only upon initial access to a new AP. Actually I wouldn't mind to return to the v0.1 clear text entry of passwords. I was trying to please.

There seems to be a wide variety of how wifi devices are initially reported. My wifi devices do not experience that which you report. However, I will in v0.4 also check for inet addr.

[gerald_clark]

The manual states:
              The  security  mode  may  be open or restricted, and its meaning
              depends on the card used. With  most  cards,  in  open  mode  no
              authentication  is  used  and  the  card  may  also  accept non-
              encrypted sessions, whereas in restricted  mode  only  encrypted
              sessions  are  accepted  and the card will use authentication if
              available.

I would take that to mean that if a key is specified, the connection should be restricted.

[coreplayer2]

I think its great to have the ability to remember and automatically connect previously connected AP's  for auto reconnects at the same location and someone who roams between the same locations repeatedly.

Thumbs up!!

[andrewb]

Minor bug:

Using the getpasswd function restricts the password length to 56 characters. WPA keys can be 63 characters

[andrewb]

Further testing shows current gettpasswd function doesn't cope with the "\" character or a space in a WPA key.

[roberts]

At this still early stage of development, I am going to concentrate on stabization and reliabilty of both WPA and WEP.  I was able to borrow a machine which is very slow to negotiate a WEP access point. So I was able to reproduce some of the reports of not connecting requiring a second run. I have added code to handle it in v0.4 and even the slow machine now connects reliably.

The demand for features is large, and I might not be able to please everyone. My goal is to keep it tiny and fast.

[coreplayer2]

Thanks, your efforts infact the efforts of all TC contributors are greatly appreciated.

:thumbs up:

[coreplayer2]

Any news on the eagerly awaited v0.4 ?

[Rich]

Hi coreplayer2
It's only been two days, and I'm sure roberts has other things he is also working on.

[roberts]

v0.4 now posted!

[coreplayer2]

Thanks  lol

The  work Roberts has put in on this extension is extremely appreciated.   this extension represents a major milestone in the seamless connectivity opening doors to places that for many would otherwise be locked out of..    there is such a dependency on wifi today that without it a pc's use is severely limited.     True there are hardwired connections but few IT departments have been maintaining their Lan's   instead they've been optimizing wifi over the last ten years,  same can be said for the home networks also.

You may configure the wpa_supplicant yourself but better have the aspirin handy!


Hat's off to roberts for taking on this worthy project and accomplishing miracles with it! 

[gerald_clark]

I'll second that.
Works good for me too.

[wget]

There is a bug when a wireless device that does not broadcast it's SSID is found first by wifi.sh.

[wget]

If the first found device has broadcast it's SSID, that's fine...