wifi.tcz

[nick65go]

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.

[roberts]

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. 

[coreplayer2]

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.

[gerald_clark]

Are you saying you just now hardcoded wlan0 or thebug was a hardcoded wlan0.
My linksys wireless adapter happens to be eth0.

[roberts]

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.

[gerald_clark]

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

[Juanito]

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.

[roberts]

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 ?

[gerald_clark]

I needed to add key restricted to line 64.

                else           
                        ifconfig ${WIFI} up               
                        sleep 2                           
                        iwconfig ${WIFI} essid ${SID} key ${KEY} key restricted
                fi

[coreplayer2]

version 0.3 already?   but it's not available here yet  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?
 

[roberts]

Use AppsAudit -> Updates  -> Check for Updates!

[coreplayer2]

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

[coreplayer2]

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.

[roberts]

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.

[roberts]

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.