Tiny Core Extensions > TCE Q&A Forum
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version