Wifi Access Gadget v0.2.0
Posted: Sun 14 Aug 2005, 14:57
WAG - Wifi Access Gadget
Version 0.0.0
Basic diagnostic listing
Version 0.1.0
Interactive command buttons
Version 0.2.0
Interactive scanning
Public release
Verions 0.3.0
Multiple wifi profiles/config save
Under development
Use on laptops in order to easily insert and eject your wireless card.
Originally written because standby/sleep ruined the PCMCIA setep.
Choose and connect to networks that do not require a key.
Also stores connection info for one secure network.
WAG REQUIRES A WORKING WIFI CARD!
If you don't know exactly what must be typed in to make you wifi work,
do not use this software. If you're tired of typing the same commands
every time your laptop wakes up, then WAG is for you.
WAG MUST BE MANUALLY CONFIGURED!
Shift left click on the WAG icon to open (not run) the Rox App.
Shift left click on the script called AppRun to open in a text editor.
Near the top you will see 'User Configured Data'.
Set CARDSOC to the socket number your Wifi card uses (usually 0 or 1).
Set WLAN to the name of your Wifi card (usually wlan0 or eth0).
If you have to load a (single) module, enter its name in MODDATA.
Set WIFIIP to your preference of IP address. It will be used whenever
possible.
Finally, there is a user customizable button in the WAG interface.
When clicked, it will run a script in the WAG directory called 'manuwifi'.
By default the button is called 'Secure WLAN' and the script contains a
template for connecting to a single encrypted access point. However, it
can also be used to store a single gateway and DNS configuration.
USING WAG
The program is slow. There is nothing you can do about it.
It varies from card to card and driver to driver, but all the tests
and probing take time. Scanning for availible networks is done
automatically and may disconnect an existing connection.
On first use, you will be presented with much information.
Some of it may look bad, but may also be meaningless. By default WAG
will check for ndiswrapper. If you don't use ndiswrapper, don't worry
when it says 'Module ndiswrapper not running'.
Other messages require immediate attention. 'Wireless card not
active' is bad. 'Wireless card not responding' is also bad. To fix this,
click 'Reseat'. Reseat will eject the card, reinsert the card, and
attempt to connect to a nearby network. When the WAG dialog returns after
a moment or two, your card should work and it should report how many
networks are in range. To choose from these networks, click 'Scan' and
choose your Cell. You can not connect to encrypted networks
through Scan.
DEBUGGING
WAG may not work with you wireless card or drivers. It was written
by one guy with one PCMCIA card and three different drivers, so it is
likely to not work for you. If WAG doesn't work, or presents you with
incorrect diagnostic information, first check to make sure you properly
entered your configuration. You didn't make any mistakes, you'll need to
post some information in the Puppy Linux forum. Tell me what was
supposed to happen and what actually happened. Tell me what you must
type in manually to form a connection. Mention what you have set the user
variables to. What do you have in rc.local to make wifi work? Most
importantly, open the WAG folder and run the 'debug' script. It will
generate a file (debug.txt) that I must have in order to make WAG work for
you.
Suggestions for functionality and interface are greatly appreciated.
Version 0.0.0
Basic diagnostic listing
Version 0.1.0
Interactive command buttons
Version 0.2.0
Interactive scanning
Public release
Verions 0.3.0
Multiple wifi profiles/config save
Under development
Use on laptops in order to easily insert and eject your wireless card.
Originally written because standby/sleep ruined the PCMCIA setep.
Choose and connect to networks that do not require a key.
Also stores connection info for one secure network.
WAG REQUIRES A WORKING WIFI CARD!
If you don't know exactly what must be typed in to make you wifi work,
do not use this software. If you're tired of typing the same commands
every time your laptop wakes up, then WAG is for you.
WAG MUST BE MANUALLY CONFIGURED!
Shift left click on the WAG icon to open (not run) the Rox App.
Shift left click on the script called AppRun to open in a text editor.
Near the top you will see 'User Configured Data'.
Set CARDSOC to the socket number your Wifi card uses (usually 0 or 1).
Set WLAN to the name of your Wifi card (usually wlan0 or eth0).
If you have to load a (single) module, enter its name in MODDATA.
Set WIFIIP to your preference of IP address. It will be used whenever
possible.
Finally, there is a user customizable button in the WAG interface.
When clicked, it will run a script in the WAG directory called 'manuwifi'.
By default the button is called 'Secure WLAN' and the script contains a
template for connecting to a single encrypted access point. However, it
can also be used to store a single gateway and DNS configuration.
USING WAG
The program is slow. There is nothing you can do about it.
It varies from card to card and driver to driver, but all the tests
and probing take time. Scanning for availible networks is done
automatically and may disconnect an existing connection.
On first use, you will be presented with much information.
Some of it may look bad, but may also be meaningless. By default WAG
will check for ndiswrapper. If you don't use ndiswrapper, don't worry
when it says 'Module ndiswrapper not running'.
Other messages require immediate attention. 'Wireless card not
active' is bad. 'Wireless card not responding' is also bad. To fix this,
click 'Reseat'. Reseat will eject the card, reinsert the card, and
attempt to connect to a nearby network. When the WAG dialog returns after
a moment or two, your card should work and it should report how many
networks are in range. To choose from these networks, click 'Scan' and
choose your Cell. You can not connect to encrypted networks
through Scan.
DEBUGGING
WAG may not work with you wireless card or drivers. It was written
by one guy with one PCMCIA card and three different drivers, so it is
likely to not work for you. If WAG doesn't work, or presents you with
incorrect diagnostic information, first check to make sure you properly
entered your configuration. You didn't make any mistakes, you'll need to
post some information in the Puppy Linux forum. Tell me what was
supposed to happen and what actually happened. Tell me what you must
type in manually to form a connection. Mention what you have set the user
variables to. What do you have in rc.local to make wifi work? Most
importantly, open the WAG folder and run the 'debug' script. It will
generate a file (debug.txt) that I must have in order to make WAG work for
you.
Suggestions for functionality and interface are greatly appreciated.