WiFi Radar creates a default configuration file if it doesn't find one at startup. This file may need to be tweaked before it can "see" any wireless access points. The built-in wireless card in my IBM ThinkPad T40 is seen by...
See more »
WiFi Radar creates a default configuration file if it doesn't find one at startup. This file may need to be tweaked before it can "see" any wireless access points. The built-in wireless card in my IBM ThinkPad T40 is seen by Ubuntu as eth0, for example, but WiFi Radar looks at eth2 in the default configuration, or at eth1 if no configuration is found. If you don't see any access points listed in the program's interface and you know they are there, edit the configuration file and make sure the line that begins interface = is pointing at the correct network adapter device. Figure 1 shows how WiFi Radar lists the connections it finds after it has been properly configured as eth0 and had profiles added. Run this way You can run WiFi Radar in two different ways: as a daemon without a user interface, or by starting it up as you would any other program. The daemon requires at least one profile in order to function correctly, and we need the UI to create a profile, so let's start there. When WiFi Radar runs normally, it displays all the available wireless networks it detects. The first time you run it, that's all it does. To connect to one of the listed access points, click on its name and then select Connect. WiFi Radar will tell you that it does not have a profile configured for the network, and ask if you want to create one. Click Yes. That brings up a new window which allows you to set various wireless options, such as mode, channel, and WEP key. You can also set a WPA driver, tweak the DHCP settings, and specify startup commands. When you're finished editing the profile, click Save. Assuming that the network likes the way you've configured it, you'll be connected to the access point. Even better, the profile will be there the next time you need it. WiFi Radar maintains its list of APs in priority order, and when run as a daemon it will automatically connect to the highest priority network that it detects. With the UI, you can change the priority of the list by dragging and dropping an AP name. The advantage of running WiFi Radar as a daemon is that you won't have to start the user interface, select the AP, and click on Connect each time you fire up the laptop. You can let the daemon do it for you. Here's an example of what you may see when you start the daemon: Some people like to run that command at boot time; I refer you to the docs for your distro for details on how to accomplish that. I can start the daemon if I'm at home or at a LUG meeting and get connected automagically, or I can start the UI if I'm on the road at a new AP. Either way, WiFi Radar gets me connected a little more quickly. Slashdot it!
See less »
Kaboodle will send you a newsletter and updates from your friends. You can unsubscribe at any time. Kaboodle does not sell or share your email address or personal information with anyone.
Kaboodle requires all users to provide their real date of birth as both a safety precaution and as a means
of preserving the integrity of the site. You will be able to hide this information from your profile if you wish.
Added by 1 people