wifi.tcz

[roberts]

Thanks for the feedback. I will take this into full consideration.

[roberts]

I am in final field testing for v0.5 which is based on v0.1 code, e.g. awk + all that I have learned along the way.

[roberts]

v0.5 is now posted.   

Also note that I have merged three separate wifi.sh  threads into one.
Please do not start separate threads for feedback. Thanks.

[pugliese]

I removed wifi.tcz- version 1 + deps Apps Auidit

I removed wifi.db

I installed the new wifi.tcz v5

did a cold restart

Did a scan with a click on the wifi icon

was presented a the bad first results on my eeepc 900a that I normally got with v2-v4

selected my access point
put in  the wep key

SUCCESS!! - did not need to do a second try.

I am happy!

will add other access points later next week when I am at my other location.

Thanks Robert!!!

[coreplayer2]

Am home now and the old notebook updated with v0.5 boots up and runs the recommended "/usr/local/bin/wifi.sh auto 2>&1 > /tmp/wifi.log" command  which connects promptly to my home network without issue.   just out of curiosity I selected to discard the connection and perform another search of available AP's, it found 29 AP's and successfully connected to my home AP when selected.

So we'll test more when out on the road again.

Thanks

[andrewb]

Robert,

Just to report:

On a EEEPC 900ax wifi.tcz doesn't work 'out-of-the-box' due to the output from iwconfig. Running iwconfig gives the output

Code: [Select]

~$ iwconfig
lo        no wireless extensions.

dummy0    no wireless extensions.

eth0      no wireless extensions.

wlan0     Ralink STA  ESSID:""  Nickname:""
              Mode:Auto  Frequency=2.412 GHz 
              Link Quality=10/100  Signal level:0 dBm  Noise level:-143 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0
                                       

So no IEEE phrase for wifi.sh to find the wireless adapter. Changing the search phrase to ESSID, everything works.

[roberts]

Actually, the IEEE test is a relic of v0.1. In v0.2 - v0.4 I had changed it
Without knowing what many and various wifi devices report when unconfigured I am now using:

WIFI="$(iwconfig 2>/dev/null | awk '{if (NR==1)print $1}')"

[roberts]

Thanks for feedback. v0.6 with corrected initial wifi device detection now posted.

[OldAdamUser2]

Robert,

I'm pleased to report that wifi.sh works perfectly on my Eee900. It allows me to get rid of wicd and all  of its dependencies, hence networking on a leaner, meaner system.

Many thanks. . . .

Actually, I may have spoken too quickly. The script runs properly and allows me to connect to my home wifi when I run it from wbar.

But, when I plug in the recommended "/usr/local/bin/wifi.sh auto 2>&1 > /tmp/wifi.log" in bootlocal.sh it does not auto-connect. If I then open a terminal window and try the command (with or without sudo), it says I don't have permission to write /tmp/wifi.log. If I delete that part of the command and try the rest, the script scans for available networks but fails to connect. But I can still go back and run the script from wbar and connect without problem. This is not a password-protected wifi.

The auto-connect that DOES work for me is--

        sudo iwconfig wlan0 essid "my-esssid#"
        sudo udhcpc -i wlan0

[roberts]

Auto connect writes to /tmp/wifi.log You should cat that file to see what happened. Based on it working from wbar would suggest that the device was not ready. You might need to add a sleep command before the wifi.sh call to allow time for the device to be created.

[coreplayer2]

Second attempt to show list of available AP's is always blank, while third attempt succeeds. This occurs when a rescan is selected. I believe we've had this issue in the past, but has been re-introduced just recently.   

This screenshot shows the second and failed (background wifi.sh window) attempt to enumerate the list of AP's,  Whereas the third successful (foreground wifi.sh window) attempt.

[bmarkus]

My experience with current and previous release that first attempt list AP's correctly but connections fails, while 2nd try is OK.

[coreplayer2]

Ok, have added above that this event occurs only when a rescan is requested.  sorry

[andrewb]

Just a quick note / question....

I noticed that the auto-connect of wifi.sh had stopped working recently after updating the extensions. Have now tracked this to a change in wifi.sh in that it now uses the flag "-a" for auto-connect rather than the word auto.

Was this change advertised anywhere other than in the info file for the extension? (a search of the forum for wifi.sh doesn't come up with anything) If not it has probably caused many people to lose the auto-connect on boot if bootlocal.sh still has "wifi.sh auto" rather than "wifi.sh -a".

Edit:

OK so found the reference at: http://forum.tinycorelinux.net/index.php/topic,14045.msg80155.html#msg80155 . Funny how a search for "wifi.sh" "-a" didn't throw this up