Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: roberts on July 02, 2011, 12:54:28 AM
-
Posted v0.2 of wifi.sh
* Major rewrite to Ash/Awk
* More robust detection of wireless devices.
* Better handling of slow to configure devices.
* Better integration with base functions.
* Auto mode is supported in /opt/bootlocal.sh or /opt/bootsync.sh
* Default (Menu) mode / Icon can display connection and optionally remove and re-scan/configure.
-
cool thanks, am gonna try it right now
:)
-
A small bug when using wpa passwords that may contain characters that are parsed by the shell. It is explained at:
http://lists.shmoo.com/pipermail/hostap/2006-February/012731.html .
I have the same setup described in the above link with a network set up via windows, in which there aren't the same restrictions on characters as in *nix. The WPA passphrase contains characters that are parsed by the shell when the wpa_passphrase command is executed in the wifi.sh script. I guess the solution is simple, but at the present time it's beyond my awk / bash scripting abilities.
-
Hi andrewb
If possible, your best bet is to stick to characters that are acceptable in both environments.
-
In an ideal world this would be good advice, but we don't live in one!! :-)
-
I will look at it for v0.3. At the moment I am busy readying Core v3.8rc1.
-
OK, one step forward: I have solved the problem for passwords with special characters. The function device_setup should be changed to :
function device_setup(t,d,s,p,c) {
if (t == "WPA") {
print p > "/tmp/wpa_ptmp"
system("wpa_passphrase " s " < /tmp/wpa_ptmp > /etc/wpa_supplicant.conf")
system("rm /tmp/wpa_ptmp")
system("wpa_supplicant -i " d " -c /etc/wpa_supplicant.conf -B")
} else {
system("iwconfig " d " essid " s " key " p" channel " c)
}
}
The stdin redirection is the only way to pass special characters to wpa_passphrase with out them being parsed by the shell. Putting the variable 'p' instead allows the shell to parse the password. I have tested this with many combinations of special characters, including those of significance to awk, and it seems to work every time. Even spaces, including those at the start & end of a password are acceptable.
The only problem now is that if the character used as a field separator in wifi.db is used in the password or ESSID it will cause problems. This can be dealt with by using a non-printing character (e.g. <BEL>) as the field separator in wifi.db. To enable this the following changes need to be made:
Change the line:
FS=":"to
FS="\7"and:
print( sid[selection] ":" password ":" type[selection] ) >> dbfileto:
print( sid[selection] "\7" password "\7" type[selection] ) >> dbfile
Now to move on to the problems of non-broadcast SSIDs........
-
I've now found that the above of course is for the original wifi.sh script, not the current one.
Back to the drawing board....
-
See: http://forum.tinycorelinux.net/index.php?topic=5287.0
You seem to want to commandeer my extension.
I should be afforded the same respect as any other extension maker.
-
Robert,
Sorry, no offence meant. Just got carried away.
Will put brain in gear before typing next time.
-
Hi Robert,
I would like to have more columns in the scanning table results, not only essid and wpa type. It is wide space enough, and maybe more default lines, like 25 lines/page (for use on a Dell mini 910).
Maybe chanel number and access point MAC address, because my neighborhoods fake the essid as BTOpenzone or BTFON, so MAC is very useful.
for your information, those two BTOpenzone or BTFON names are FREE wifi in UK, if you (or one of your friend) have an BT or FON account for broadband in UK (BT is partner with OPenzone etc). So if you travel in Spain, for example, you can use for free any wifi spot from BTOpenzone, no need to pay for hotel/airport/caffe wifi...
Thank you.
-
hello friends,
i want to report my problems with the latest wifi.tcz, although the wifi-connection with cnetworkmanager works proberly.
sudo /usr/local/etc/init.d/dbus start
sudo /usr/local/etc/init.d/NetworkManager start
sudo cnetworkmanager --connect=<access-point-essid> --wpa-pass=<wpa2-password>
when i start wifi.tcz, all access-points are scanned and listed in my terminal.
after choosing my access-point f.e. "access-point-essid", the access-point is called "Desktop" or another file that is stored in my home-directory.
then the terminal asks me for the password twice (my password-input is masked), but there is no positive result or a connection at the end.
on the other side: if i use the network-starterpack, the access-point is named correctly, the password-input is only once and unmasked, and at the very end the setup of the wifi-connection succeeds.
does anyone confirm this behaviour?
is someone able to automate the start or restart of dbus and NetworkManager, that it just works?
sometimes i have to restart them a couple of times... does anyone know reasons?
-
Hi Robert,
I would like to have more columns in the scanning table results, not only essid and wpa type. It is wide space enough, and maybe more default lines, like 25 lines/page (for use on a Dell mini 910).
Maybe chanel number and access point MAC address, because my neighborhoods fake the essid as BTOpenzone or BTFON, so MAC is very useful.
for your information, those two BTOpenzone or BTFON names are FREE wifi in UK, if you (or one of your friend) have an BT or FON account for broadband in UK (BT is partner with OPenzone etc). So if you travel in Spain, for example, you can use for free any wifi spot from BTOpenzone, no need to pay for hotel/airport/caffe wifi...
Thank you.
Interesting to note. I had channel in v0.1 and was told that it is not needed.
How would you know about a MAC address? That request seems odd to me.
-
hello friends,
i want to report my problems with the latest wifi.tcz, although the wifi-connection with cnetworkmanager works proberly.
sudo /usr/local/etc/init.d/dbus start
sudo /usr/local/etc/init.d/NetworkManager start
sudo cnetworkmanager --connect=<access-point-essid> --wpa-pass=<wpa2-password>
when i start wifi.tcz, all access-points are scanned and listed in my terminal.
after choosing my access-point f.e. "access-point-essid", the access-point is called "Desktop" or another file that is stored in my home-directory.
then the terminal asks me for the password twice (my password-input is masked), but there is no positive result or a connection at the end.
on the other side: if i use the network-starterpack, the access-point is named correctly, the password-input is only once and unmasked, and at the very end the setup of the wifi-connection succeeds.
does anyone confirm this behaviour?
is someone able to automate the start or restart of dbus and NetworkManager, that it just works?
sometimes i have to restart them a couple of times... does anyone know reasons?
The wifi.sh is not to be used with dbus, networkmanager, or any other. It is a stand-a-lone minimal scanning and auto connect wifi tool.
You are confusing v0.1 with v0.2. Some want channel number, so do not. Some want enter clear text passwords some do not. I know that I will never please all. But note, wifi.sh is only an option. You are free to use many wifi network managers in the repository.
My goal for wifi.sh is to have the smallest wifi tool to scan and provide auto connect at boot.
Obviously it works for me and friends that helped test it.
It is still in early development. Obviously I do not have access to a wide range of hardware to test.
I will take in ideas for v0.3 and you may wish to try that when available.
Please don't feel that there is any requirement to use wifi.sh and don't mix with exiting wicd, networkmanager or others that try to do the same thing.
-
thank you robert for your reply.
i will love to test the future versions...
now after some commands in the terminal i get my wifi-connection, so that's ok.
you have to know, i'm a heavy tester, i'm really happy to use tinycore in different situations and configurations,
so perhaps i can give some hints!?
-
I vote for any more info in the resulting output. How should I know what essid ap to link if more have the same name?. (And about MAC, I keep a text list of bad habits neighborhoods, as there are just few near my fix location). It will not hurt more info to differentiate from just a list of results, thanks.
Also, if udhcpc fail to assign an IP from wifi.sh, then I must manually run top in aterm to check and sudo pkill wpa* all 3 insistence of wpa_supplicant -B from RAM; Plus if I run wifi.sh few times consecutive, a longer/shorter list will appear, not necessarily the same all the time. I understand that wifi.sh is just a tool work in progress, but I will prefer not to copy the logic of wifi (which I do now :-\) for my own wifi start script.
-
Still early in the development. Found and fixed a bug, hard coded, wlan0.
I am cleaning up any extra wpas! I have added some ideas already posted regarding special characters.
Thanks for feedback. Please have patience.
-
Great job thanks roberts
I agree to not including too much information, it's not needed for the majority. In any case the mac of the AP's are easily obtained for those who feel they need it.
-
Are you saying you just now hardcoded wlan0 or thebug was a hardcoded wlan0.
My linksys wireless adapter happens to be eth0.
-
In v0.2 line 102 had wlan0 and so therefore some where seems multiple wpa_supplicants running.
v0.3 now posted, mainly a bug fix, db delimiter changed to tab & shell protect WPA password.
You must clear out (rm ) your wifi.db.
-
Now when I boot with 'wifi.sh auto', the access point is found.
Udhcpc is run 3 times, but no IP address is assigned.
ps -x shows no udhcpc running.
I run 'wifi.sh auto' again, and I get my IP address.
ps -x shows:
udhcpc -n -i eth0
-
Udhcpc is run 3 times, but no IP address is assigned.
ps -x shows no udhcpc running.
This is the normal behavior for udhcpc - I mean if you run the command manually and it doesn't get an ip address it will try three times and then give up.
..which probably means it didn't get a response from your router the first time.
-
Now when I boot with 'wifi.sh auto', the access point is found.
Udhcpc is run 3 times, but no IP address is assigned.
ps -x shows no udhcpc running.
I run 'wifi.sh auto' again, and I get my IP address.
ps -x shows:
udhcpc -n -i eth0
Does it help if you increase the TRY loop from 3 to perhaps 5 or higher at line 70 ?
-
I needed to add key restricted to line 64.
else
ifconfig ${WIFI} up
sleep 2
iwconfig ${WIFI} essid ${SID} key ${KEY} key restricted
fi
-
version 0.3 already? but it's not available here yet http://distro.ibiblio.org/tinycorelinux/3.x/tcz/src/ (http://distro.ibiblio.org/tinycorelinux/3.x/tcz/src/) Kinda catch twenty two situation. We can't download it from the official source and can't use the app-browser to download when a copy of it is already installed and required for the connection??
Maybe I'll try the network starter pack for a temporary connection while using the app-browser to get wifi v0.3?
-
Use AppsAudit -> Updates -> Check for Updates!
-
lol I'm not used to all these options yet. :)
I succeeded by temporarily loading up network starter-pack to replace the deleted wifi app with the new version, thanks
-
I had been investigating the multiple wpa_supplicants and had figured there were still some remnants of previous wifi connection managers to be removed, am pleased to report I no longer have multiple wpa_supplicant instances running.
:)
-
I needed to add key restricted to line 64.
else
ifconfig ${WIFI} up
sleep 2
iwconfig ${WIFI} essid ${SID} key ${KEY} key restricted
fi
Hopefully that is universal.
-
I had been investigating the multiple wpa_supplicants and had figured there were still some remnants of previous wifi connection managers to be removed, am pleased to report I no longer have multiple wpa_supplicant instances running.
:)
Thanks for feedback. Hopefully wifi.sh will work for many by the time 3.8 goes gold.
-
Am not sure you this feedback was ever found from v0.2 from here http://forum.tinycorelinux.net/index.php?topic=10283.msg55735#msg55735 (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.
-
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.
-
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.
-
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!!
-
Minor bug:
Using the getpasswd function restricts the password length to 56 characters. WPA keys can be 63 characters
-
Further testing shows current gettpasswd function doesn't cope with the "\" character or a space in a WPA key.
-
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.
-
Thanks, your efforts infact the efforts of all TC contributors are greatly appreciated.
:thumbs up:
-
Any news on the eagerly awaited v0.4 ?
-
Hi coreplayer2
It's only been two days, and I'm sure roberts has other things he is also working on.
-
v0.4 now posted!
-
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! :)
-
I'll second that.
Works good for me too.
-
There is a bug when a wireless device that does not broadcast it's SSID is found first by wifi.sh.
(http://files.myopera.com/huohulwz/albums/7932772/1.png)
-
If the first found device has broadcast it's SSID, that's fine...
(http://files.myopera.com/huohulwz/albums/7932772/3.PNG)
-
And the new wifi.sh version is better than the original wifi.sh, then I switch a Wifi network and ignore the characters that are parsed by the shell.
original version:
(http://files.myopera.com/huohulwz/albums/7932772/5.PNG)
version 2011-07-14:
It's will not work like ... , -2, -1, 0, 1, ... even the unexpected characters appear.
-
Actually, I can del this chars and choose what I want, but with the SSID-less-Wifi-Network,
the string will be shifted, and work like that
(http://files.myopera.com/huohulwz/albums/7932772/06.PNG)
original version:
(http://files.myopera.com/huohulwz/albums/7932772/04.PNG)
That's all, how to deal with the Wifi-Network that hide SSID?
-
No claim to any support for hidden sid.
Use any of the many network managers currently in the repo.
-
I used Apps Audit to look for updates and updated wifi.tcz.
I activated wifi.tcz and the usual Access Points were identified.
I selected the access point I normally use and I was asked for a password and to re enter it again.
The password was accepted but it could not associate it with the access point.
It has been working perfectly with the prior version.
Can I still get the prior version or is there something I should try.
edited subject line corrected to wifi.tcz
-
As I kept copies of the four versions so far I'm attaching an archive that contains all of them (with dates in their respective file names).
It is crucial that you report back (with specific details) your findings if it turns out that an older version works better for you to give Robert a chance to get to the bottom of it.
-
Maro,
I need some help. Normally I copy a .tcz file to tce/optional. What should I do with the tgz file. Do I need to create a wifi.tcz file using the wifi.tgz file. Is there another way to install the tgz file.
Thanks,
Tony
-
A tgz file is like a zip file - I presume the previous versions of wifi.tcz are to be found inside.
Copy the tgz file to /tmp, "cd /tmp" and then "tar xzf *.tgz" you should then see the contents of the tgz file in /tmp
-
Maro,
wifi_110615.tcz is successful
wifi_110710.tcz and wifi_110702.tcz both fail with the following message:
no lease failing
retries 3 times and
fails
wifi_110714 fails with the following message:
Trying to associate with access point ...
let me know if you need additional information
-
I selected the access point I normally use and I was asked for a password and to re enter it again.
The password was accepted but it could not associate it with the access point.
How long is your password?
Does it contain any 'special' characters? e.g.: forward or back slash ( \ / ), quote marks ( " ') or $
-
10
no special char
-
The first version is using a database that is not compatible with subsequent versions.
Using the latest version please open an xterm and run wifi.sh.
Take a screenshot and post here.
-
I removed my wifi.tcz with AppsAudit
Installed current version of wifi.tcz using Apps
I used sudo wifi.sh to run the application
TRY 1 failed
TRY 2 was successful
following is the output of the two tries I ran using
Note in TRY1
- Strength is 70 for all access points
- my target is item 13
Note in TRY2
- Strength is unique for each access point and in descending order
- my target is item 1
I restarted tcl several times and found the same pattern- failure/success- after selecting my access point and failing, subsequent tries succeeded.
------------------------------------------------------------------------------------------------------------------------------
TRY 1
------------------------------------------------------------------------------------------------------------------------------
Found wifi device wlan0
Standby for available networks...
Select Wifi Access Point
1. svs on 70
2. shamrock on 70 WPA
3. selizab on 70
4. pappawabbit on 70
5. jardin on 70
6. hpsetup off 70
7. dean on 70
8. chopnet on 70 WPA
9. carmfro on 70 WPA
10. NETGEAR_1955_36 on 70 WPA
11. MuckipLuvsPatron on 70 WPA
12. FastCar on 70
13. 2WIRE572 on 70
14. 2WIRE330 on 70 WPA
15. Noppe's tachyon beam on 70 WPA
Enter selection from (1-15) or (q)uit:1
Enter Passwprd (8 tp 56 characters) for 2WIRE572:********** Re-enter:**********
*** Accepted.
Trying to associate with 2WIRE572..........................could not associate with
2WIRE572.
----------------------------------------------------------------------------------------------------------------
TRY2
-----------------------------------------------------------------------------------------------------------------
Found wifi device wlan0
Standby for available netowrks...
Select Wifi Access Point
1. 2WIRE572 on 57
2. 2WIRE330 on 24 WPA
3. MuckipLuvsPatron on 22 WPA
4. SFHAwifi off 21
5. NETGEAR_1955_36 on 21 WPA
6. FastCar on 20
7. dean on 17
8. svs on 15
8. HP8C3E9E on 15
10. selizab on 14
11. hpsetup off 13
12. 2WIRE598 on 10
13. John Mola's Network on 20 WPA
Enter selection from (1-15) or (q)uit:1
Enter Passwprd (8 tp 56 characters) for 2WIRE572:********** Re-enter:**********
*** Accepted.
Trying to associate with 2WIRE572...Success.
Requesting IP.
udhcpc (v1.18.3) started
Sending discover...
Sending select for 192.168.1.76...
Lease of 192.168.176 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 192.168.1.254
Success
-
From output seems like your initial iwlist is not reporting correctly.
From a cold boot (power off & reboot) open an xterm and type
iwlist wlan0 scanning
Check to see if the initial iwlist is reporting all APs at the same signal strength. Post output here.
iwlist is the standard utility to generate your AP pick list.
-
power off and reboot:
iwlist wlan0 scanning
wlan0 Failed to read scan data: Network is down
sudo iwlist wlan0 scanning
wlan0 Interface doesn't support scanning: Network is down
-
Please try:
sudo iwlist wlan0 scanning
-
Hi roberts
Please try:
sudo iwlist wlan0 scanning
pugliese mentioned that one in the previous post.
-
output:
wlan0 Interface doesn't support scanning : Network is down
-
OK. That is expected. Now please try the following two commands after a cold boot and post the results...
sudo ifconfig wlan0 up
sudo iwlist wlan0 scanning
As a separate test, please try, after a cold boot, using the latest wifi.sh v04 the following:
In your previous posts you showed a successful connection after a 2nd try. Therefore your network specifics should be stored in wifi.db, please verify (cat wifi.db), then issue the following command and post results.
sudo wifi.sh auto
-
input 5 actions that produced indicated output
1. did a cold boot
2. sudo ifconfig wlan0 up
3. sudo iwlist wlan0 scanning
(output)
wlan0 Scan completed :
Cell 01 - Address: C0:3F:0E:71:BF:12
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=22/70 Signal level=-88 dBm
Encryption key:on
ESSID:"carmfro"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=000000a0f611219c
Extra: Last beacon: 1186ms ago
IE: Unknown: 00076361726D66726F
IE: Unknown: 010882840B162430486C
IE: Unknown: 030101
IE: Unknown: 050401030000
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: 2D1A7C181BFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1601001300000000000000000000000000000000000000
IE: Unknown: DD0E0050F204104A0001101044000102
IE: Unknown: DD090010180202F0050000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C337C181BFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C3401001300000000000000000000000000000000000000
Cell 02 - Address: 00:23:69:56:B1:48
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=15/70 Signal level=-95 dBm
Encryption key:on
ESSID:"pappawabbit"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000000155361d7
Extra: Last beacon: 1176ms ago
IE: Unknown: 000B7061707061776162626974
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 0504FF010000
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: 2D1A1C181AFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1601001700000000000000000000000000000000000000
IE: Unknown: 7F0101
IE: Unknown: DD0E0050F204104A0001101044000102
IE: Unknown: DD090010180203F4010000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C331C181AFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C3401001700000000000000000000000000000000000000
Cell 03 - Address: 32:EF:8F:7E:F7:E4
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=21/70 Signal level=-89 dBm
Encryption key:off
ESSID:"HP8C3E9E"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Ad-Hoc
Extra:tsf=00000126575c7bfe
Extra: Last beacon: 1156ms ago
IE: Unknown: 00084850384333453945
IE: Unknown: 010482848B96
IE: Unknown: 030101
IE: Unknown: 06020000
IE: Unknown: 0706555320010B14
IE: Unknown: 2A0100
IE: Unknown: 32080C1218243048606C
Cell 04 - Address: 00:1A:04:FD:75:01
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=62/70 Signal level=-48 dBm
Encryption key:on
ESSID:"2WIRE572"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000000de52729985
Extra: Last beacon: 1033ms ago
IE: Unknown: 00083257495245353732
IE: Unknown: 010882848B0C12961824
IE: Unknown: 030101
IE: Unknown: 0706555320010B1B
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
Cell 05 - Address: 00:09:5B:6F:C1:CC
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=16/70 Signal level=-94 dBm
Encryption key:off
ESSID:"derfla"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Mode:Master
Extra:tsf=0000002913d39185
Extra: Last beacon: 1136ms ago
IE: Unknown: 0006646572666C61
IE: Unknown: 010482848B96
IE: Unknown: 030101
IE: Unknown: 0406010200000000
IE: Unknown: 05050001000013
Cell 06 - Address: 00:15:6D:F8:C1:5C
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=19/70 Signal level=-91 dBm
Encryption key:off
ESSID:"SFHAwifi"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000000103fc8cd80
Extra: Last beacon: 1133ms ago
IE: Unknown: 00085346484177696669
IE: Unknown: 010882848B960C121824
IE: Unknown: 030101
IE: Unknown: 050400010000
IE: Unknown: 2A0100
IE: Unknown: DD26000C42000000011E000000001F660902FF0F617038312D6E6F72746862656163000000000000
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101820003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C334C101BFFFF000000000000000000000000000000000000000000
IE: Unknown: 2D1A4C101BFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C3401001900000000000000000000000000000000000000
IE: Unknown: 3D1601001900000000000000000000000000000000000000
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD0A00037F04010002004000
IE: Unknown: DD0E00156D0000000102B2E102021200
Cell 07 - Address: 98:FC:11:57:88:6E
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=21/70 Signal level=-89 dBm
Encryption key:on
ESSID:"MudkipLuvsPatron"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=000000969cddd18c
Extra: Last beacon: 1150ms ago
IE: Unknown: 00104D75646B69704C757673506174726F6E
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 050400010000
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: 2D1A7C181BFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1601001300000000000000000000000000000000000000
IE: Unknown: 4A0E14000A002C01C800140005001900
IE: Unknown: 7F0101
IE: Unknown: DD0E0050F204104A0001101044000102
IE: Unknown: DD090010180202F0040000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
Cell 08 - Address: 00:11:24:63:09:7B
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=18/70 Signal level=-92 dBm
Encryption key:off
ESSID:"Sphere'N"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000006f0696045d
Extra: Last beacon: 906ms ago
IE: Unknown: 0008537068657265274E
IE: Unknown: 010C82848B8C12969824B048606C
IE: Unknown: 030103
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: DD0700039301660000
IE: Unknown: DD06001018020000
Cell 09 - Address: 00:14:6C:EF:C2:58
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=38/70 Signal level=-72 dBm
Encryption key:off
ESSID:""
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000008e7a38183
Extra: Last beacon: 893ms ago
IE: Unknown: 0006000000000000
IE: Unknown: 010882848B962430486C
IE: Unknown: 030103
IE: Unknown: 0504FF030000
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: 2D1A1C181AFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1603080000000000000000000000000000000000000000
IE: Unknown: 7F0101
IE: Unknown: DD090010180200F0010000
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C331C181AFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C3403080000000000000000000000000000000000000000
Cell 10 - Address: 00:18:F8:6F:E6:FD
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=10/70 Signal level=-100 dBm
Encryption key:on
ESSID:"chopnet"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000004acfa918a
Extra: Last beacon: 806ms ago
IE: Unknown: 000763686F706E6574
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: DD06001018020014
Cell 11 - Address: 00:18:4D:4D:A1:AA
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=21/70 Signal level=-89 dBm
Encryption key:on
ESSID:"FastCar"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s
Bit Rates:9 Mb/s; 18 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000069636c67e00
Extra: Last beacon: 780ms ago
IE: Unknown: 000746617374436172
IE: Unknown: 010882848B960C183048
IE: Unknown: 030106
IE: Unknown: 2A0100
IE: Unknown: 32041224606C
IE: Unknown: DD0900037F0101001DFF7F
IE: Unknown: DD0C00037F020101240002534000
IE: Unknown: DD1A00037F030100000000184D4DA1AA02184D4DA1AA64002C011D08
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
-
Cell 12 - Address: 06:1B:63:18:1A:BF
Channel:7
Frequency:2.442 GHz (Channel 7)
Quality=9/70 Signal level=-101 dBm
Encryption key:on
ESSID:"Noppe's Guest Network"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000001f0e88b8044
Extra: Last beacon: 726ms ago
IE: Unknown: 00154E6F7070652773204775657374204E6574776F726B
IE: Unknown: 010882848B960C121824
IE: Unknown: 030107
IE: Unknown: 0706555320010B1E
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 2D1AAC4117FFFFFF0000000000000000000000000000000000000000
IE: Unknown: 3D1607000000000000000000000000000000000000000000
IE: Unknown: DD180050F2020101020003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C33AC4117FFFFFF0000000000000000000000000000000000000000
IE: Unknown: DD1A00904C3407000000000000000000000000000000000000000000
IE: Unknown: DD1700039301710008000E001B63181ABF07001B63181AC095
IE: Unknown: DD070017F203020180
Cell 13 - Address: 3C:EA:4F:52:7D:91
Channel:8
Frequency:2.447 GHz (Channel 8)
Quality=20/70 Signal level=-90 dBm
Encryption key:on
ESSID:"2WIRE330"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000000aba002c181
Extra: Last beacon: 606ms ago
IE: Unknown: 00083257495245333330
IE: Unknown: 010882848B0C12961824
IE: Unknown: 030108
IE: Unknown: 0706555320010B1B
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
Cell 14 - Address: 66:2A:2F:53:7C:99
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=10/70 Signal level=-100 dBm
Encryption key:off
ESSID:"hpsetup"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Mode:Ad-Hoc
Extra:tsf=ffffffe4f979998c
Extra: Last beacon: 466ms ago
IE: Unknown: 000768707365747570
IE: Unknown: 010482848B96
IE: Unknown: 03010B
IE: Unknown: 06020000
IE: Unknown: DD050010180100
Cell 15 - Address: 00:17:3F:BD:71:4E
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=16/70 Signal level=-94 dBm
Encryption key:on
ESSID:"dean"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000020bcc9625e7
Extra: Last beacon: 483ms ago
IE: Unknown: 00046465616E
IE: Unknown: 010482848B96
IE: Unknown: 03010B
IE: Unknown: 0406000200000000
IE: Unknown: 2A0102
IE: Unknown: 32080C1218243048606C
Cell 16 - Address: C0:3F:0E:76:61:4F
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=20/70 Signal level=-90 dBm
Encryption key:on
ESSID:"NETGEAR_1955_36"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000c55179f1a
Extra: Last beacon: 963ms ago
IE: Unknown: 000F4E4554474541525F313935355F3336
IE: Unknown: 010882848B960C121824
IE: Unknown: 030103
IE: Unknown: 050402030000
IE: Unknown: 0706555320010B1B
IE: Unknown: 2A0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101820003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C334E111BFF00000000000000000000000000000000000000000000
IE: Unknown: 2D1A4E111BFF00000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C3403051900000000000000000000000000000000000000
IE: Unknown: 3D1603051900000000000000000000000000000000000000
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD0A00037F04010002004000
IE: Unknown: DD0E0050F204104A0001101044000102
Cell 17 - Address: C0:3F:0E:95:E6:B6
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=9/70 Signal level=-101 dBm
Encryption key:on
ESSID:"selizab"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=000001f0eacc1f6b
Extra: Last beacon: 820ms ago
IE: Unknown: 000773656C697A6162
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 050400030000
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: DD090010180201F0000000
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
Cell 18 - Address: 00:0F:66:D7:4C:75
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=17/70 Signal level=-93 dBm
Encryption key:on
ESSID:"svs"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000008a2a245684
Extra: Last beacon: 793ms ago
IE: Unknown: 0003737673
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: DD050010180100
Cell 19 - Address: 00:22:3F:A5:3B:BB
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=9/70 Signal level=-101 dBm
Encryption key:on
ESSID:"GoMets"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000004dcce12a5e
Extra: Last beacon: 786ms ago
IE: Unknown: 0006476F4D657473
IE: Unknown: 010882848B0C12961824
IE: Unknown: 030106
IE: Unknown: 0706444520010D14
IE: Unknown: 200100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: Unknown: 2A0102
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101820003A4000027A4000042435E0062322F00
IE: Unknown: DD0900037F0101003DFF7F
IE: Unknown: DD1A00037F030100000000223FA53BBB06223FA53BBB64002C013D08
Cell 20 - Address: 00:1C:DF:CC:F6:88
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=13/70 Signal level=-97 dBm
Encryption key:on
ESSID:"Sacramento15"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=000001264a179183
Extra: Last beacon: 510ms ago
IE: Unknown: 000C53616372616D656E746F3135
IE: Unknown: 010882848B962430486C
IE: Unknown: 03010B
IE: Unknown: 050400010000
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: DD0E0050F204104A0001101044000102
IE: Unknown: DD090010180200F0000000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
Cell 21 - Address: D8:30:62:31:4F:A1
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=18/70 Signal level=-92 dBm
Encryption key:on
ESSID:"John Mola's Network"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000020ba5ee4177
Extra: Last beacon: 343ms ago
IE: Unknown: 00134A6F686E204D6F6C612773204E6574776F726B
IE: Unknown: 010882848B960C121824
IE: Unknown: 03010B
IE: Unknown: 050401030000
IE: Unknown: 0706555320010B1E
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 2D1A2C4017FFFF000000000000000000000000000000000000000000
IE: Unknown: 3D160B001100000000000000000000000000000000000000
IE: Unknown: DD180050F2020101010003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C332C4017FFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C340B001100000000000000000000000000000000000000
IE: Unknown: DD07000393016B0120
IE: Unknown: DD070017F203020180
**********************************************
4. cat wifi.db
(output)
access point (password indicated)
5. sudo wifi.sh auto
(output)
Found wifi device wlan0
Standby for scan of available networks....
**********************************************
-
I captured your scan ouput from cold boot and ran it through the awk parser resulting in:
2WIRE572 on 62
carmfro on 22 WPA
MudkipLuvsPatron on 21 WPA
HP8C3E9E off 21
FastCar on 21
NETGEAR_1955_36 on 20 WPA
2WIRE330 on 20 WPA
SFHAwifi off 19
Sphere'N off 18
svs on 17
derfla off 16
dean on 16
pappawabbit on 15 WPA
Sacramento15 on 13 WPA
hpsetup off 10
chopnet on 10
selizab on 9
GoMets on 9 WPA
Noppe's Guest Network on 9 WPA
John Mola's Network on 18 WPA
So I am not able to reproduce your "bad" first results.
If you netcard scan produces inconsistent results then I will not be able to handle. I suppose if you see bad scan results, quit from select, and try again.
On your step 5.
I was wanting to see the results from a cold boot of ...
sudo wifi.sh auto
-
sudo wifi.sh auto
(output)
Found wifi device wlan0
Standby for scan of available networks....
This is all I could see even piped it to a file and got nothing more.
I also tried a usb wifi adapter based on a different chip set and driver on another computer and had the same problem of getting a connection on the second try. I also changed routers with no luck
I also used a memory stick install instead of a frugal install and got the same results.
-
I put together a USB install to show off tinycore to a colleague, using the 3.8rc and the network starter kit..
Guess what? while the listing of AP's is perfect I have exactly the same connection issue, scans and detects AP's but absolutely would not connect. thanks for the post with previous wifi builds I used each one until finally the last one (wifi_110615.tcz) connected immediately. Am typing this using the connection created with wifi_110615.tcz extension, whilst no other version would associate with an AP..
With the version fromAfter selecting the access point the script echo's "Trying to associate with access point ...". Then " could not associate with ap" or something like that.
-
Did you try a second time? WEP or WPA?
After failure please post the output of iwconfig wlan0?
-
Yes second, third and more times.. the result was always the same "can not associate with ap" with the later version and "connection failed" errors with earlier versions.
The AP was open, completely unsecured. There were two AP's at this remote location; one a one word ssid, the other stronger ap ssid comprised three words with spaces between each.
Access points were always visible and clearly defined no matter which which version of wifi was used. (each version was installed and loaded after a reboot) I followed the same procedure with each version.
-
I'm such a mobile guy that who knows when I'll return to the prior mentioned location.
Well, I've since tried connecting at two other locations today without issue. I'll continue monitor the situation and advise. I'll post the iwconfig wlan0 results next time
Only thing worth considering, it's possible that some other components belonging to other connection managers which I'd forgotten to remove may have caused the conflict??
-
Thanks for detailed feedback. Embedded spaces in ssid is a problem and will be addressed in next cut.
-
Robert,
I installed wifi.tcz v4 using Apps on a different computer and used a wireless usb adapter based on rtl8187 instead of the built in wireless adapter that was giving me bad first results on my asus 900a
The scan gave me good results with access points listed in the order of strength. But a connection still could not be made on the first try.
A connection was successful ,however, on the second try.
Here is the iwconfig wlan0 results of the failed try:
wlan0 IEEE 802.11bg ESSID:"2WIRE572"
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:offs
-
Hmm. That is interesting because wifi.sh has been field tested on two different 900a eeepcs.
Could it be that you also require spaces in the ssid? I am working to support that feature.
-
I did not see any essids with spaces.
To make sure I relocated to a more controlled environment with normally 2 access points and retested
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Select Wifi Access Point
1. 2WIRE851 on 46
2. 2WIRE556 on 36 WPA
Enter selection ( 1 - 2 ) or (q)uit:
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
I used the rtl8187 wireless adapter and again.
first try : good scan with valid strengths ( see above) , but failure to associate with 2WIRE851
second try : Success
This happens on 3 different computers. All coexisting with Foresight Linux.
wifi.tcz ver 1 does not have this condition. It always works correctly
-
Thanks for the feedback. I will take this into full consideration.
-
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.
-
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.
-
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!!!
-
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
-
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~$ 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.
-
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}')"
-
Thanks for feedback. v0.6 with corrected initial wifi device detection now posted.
-
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
-
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.
-
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.
(http://db.tt/Wq8Y4eOZ)
-
My experience with current and previous release that first attempt list AP's correctly but connections fails, while 2nd try is OK.
-
Ok, have added above that this event occurs only when a rescan is requested. sorry
-
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