Tiny Core Extensions > TCE Q&A Forum
wifi.tcz
nick65go:
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.
netnomad:
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?
roberts:
--- Quote from: nick65go on July 08, 2011, 11:08:11 AM ---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.
--- End quote ---
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.
roberts:
--- Quote from: netnomad on July 08, 2011, 04:30:20 PM ---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?
--- End quote ---
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.
netnomad:
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!?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version