Wireless Assistant
Network
Description:

Wireless Assistant (wlassistant) is a small application that allows you to connect to wireless networks.

* MAIN FEATURES:
- WPA-PSK Encryption Support (WPA/WPA2)
- WEP Encryption Support
- Not Broadcasted ("hidden") ESSIDs Support
- Per Network (AP) Configuration Profiles
- Automatic (DHCP, both dhcpcd and dhclient) and manual configuration options.
- Connection status monitoring.

* MAIN REQUIREMENTS:
- wireless-tools 27 or newer (with iwlib)
- dhcpcd or dhclient
- sudo
- wpa_supplicant with wpa_cli for WPA-PSK support

* Example sudo config: If you want to e.g. allow all users from some group to use wlassistant, add the following line to your /etc/sudoers:
%{group_name} ALL=NOPASSWD: {path_to_kde}/bin/wlassistant

* MADWIFI WPA-PSK: If your card uses a madwifi driver, make sure it's madwifi-ng.
* NDISWRAPPER WPA-PSK: make sure you use ndiswrapper version newer than 1.13.

Changelog:

9 years ago

*** RELEASE 0.5.7:
* NOTE: This release includes some brand new or rewritten features. Please submit bugs to sf.net page and comments/votes here. Thanks!

* NEW: Finally WPA-PSK support (WPA/WPA2, please test and report in case of problems!)
* NEW/FIX: Rewritten, completely new connection state detection (please comment!)
* NEW: Optional grouping of APs with the same ESSID
* FIX: UI refinements
* FIX: hide encryption keys in console output and edit dialogs
* FIX: Connection using dhclient fails
* FIX: don't check for connection while wizard is running
* FIX: remove default gateway upon disconnection if not managed by DHCP client
* FIX: updated Polish translation (with help from riklaunim)
* FIX: Many internal changes, more stable

11 years ago

bushwakko

I had a problem with WEP, turns out the AP i connected to had WEP set up with ASCII, so the password "abcde" was actually "6162636465". I had to use password "6162636465" for it to work, but in windows abcde works just fine. Seems like windows detects that the password should be ASCII and then translates it? I spent a few days working on it, only when I checked the AP (which I didnt set up, I figured it out).

Report

11 years ago

pnawrocki

Hi!
I'm not sure about this answer since I had no chance to test it, so consider it a guess:
wlassistant accepts any WEP key that iwconfig does. AFAIK iwconfig supports ASCII keys. You should just prepend "s:" to it. That would be "s:abcde" in your case. Let me know if it works!

Report

11 years ago

sambo57u

Some distributions are naming their
dhclient files with -ethX extension e.g.
/var/run/dhclient-eth1.pid . When I run
dhclient it misses these and things dhclient
is not running BUT puts a message saying
that we can put the explicit name in to
wlassistantrc file. I could not find any
template for this file, not its location.

Report

11 years ago

pnawrocki

Hi!
wlassistantrc can be found in ~/.kde/share/config/
In your case set the set the following line in the wlassistantrc [Paths] section:
DHCP PID File (dhclient)=/var/run/dhclient-%1.pid
'%1' will be substituted with the interface name. Let me know if you succeeded!
NOTE: b/c wlassistant uses sudo, you might need to be root to edit this file.

Report

11 years ago

sambo57u

Yes. Thank you. Doing what you said
fixed the problem.

What would be nice is to have a system
wide wlassistantrc file, say in /etc

Report

11 years ago

mehmetb

Works Great. I hate when the initialization scripts looks for a wireless network and spends minutes when there is none! So, just compile this magnificant program, cancel the "start at boot" option of the wireless connection, and enjoy the fast boot up and have the freedom to select your favorite wireless connection. Don't forget the "sudo" stuff though!!

Thank god we have it at last, I was starting to get worried ;) Thanks buddy.

Report

11 years ago

Xastor

Impressively usefull utility! I've been searching for one like it for a long time now. Until now I used to manually scan, config and run dhcpcd. As far as I know, there's no other utility doing network scanning and network configuration at once in such a clean way. Thank you for your time and effort, creating this utility!

Report

11 years ago

pnawrocki

Thanks for that comment!
Motivation boosters are exactly what I need to keep working on the app.
Cheers.

Report

11 years ago

ChaKy

I know, it's not a question about application, but could you write me the name or a color scheme that you are using here? Thanks.

Report

11 years ago

pnawrocki

Hi.
It's the one I created myself, so you may consider it a noname. Sent it to you by email.

Report

11 years ago

Marshalle

Could you please add a version number somewhere in the GUI when running wlassistant? I feel it would be handy to know a) what version you currently have and b) confirmation that an upgrade has worked successfully.

Report

11 years ago

pnawrocki

ok, will thing about it. Till then, you can run 'wlassistant --version' in the console.

Report

11 years ago

jhorey

Many AP's these days support WPA these days instead of WEP. Although using wpa_supplicant is easy enough, it would be nice for wlassistant to be able to input shared WPA keys. So far this program looks great.

Report

11 years ago

pnawrocki

It is planned for the 0.6.0 release.

Report

11 years ago

gnemmi

Am I missing something to compile 0.5.4??
Maybe some new headers or a new lib or something ?

if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/lib/kde3/include -I/usr/lib/qt3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -MT waconfig.o -MD -MP -MF ".deps/waconfig.Tpo" -c -o waconfig.o waconfig.cpp; \
then mv -f ".deps/waconfig.Tpo" ".deps/waconfig.Po"; else rm -f ".deps/waconfig.Tpo"; exit 1; fi
En el fichero incluído de /usr/include/iwlib.h:127,
de watools.h:21,
de watools.cpp:21:
/usr/include/linux/socket.h:1:2: aviso: #warning "You should include . This time I will do it for you."
En el fichero incluído de /usr/include/wireless.h:75,
de /usr/include/iwlib.h:131,
de watools.h:21,
de watools.cpp:21:
/usr/include/linux/socket.h:1:2: aviso: #warning "You should include . This time I will do it for you."
En el fichero incluído de watools.cpp:24:
/usr/include/linux/socket.h:1:2: aviso: #warning "You should include . This time I will do it for you."
watools.cpp: En static member function `static char* WATools::ap(const char*)':
watools.cpp:52: error: `iw_sockets_close' undeclared (first use this function)
watools.cpp:52: error: (Each undeclared identifier is reported only once for
each function it appears in.)
watools.cpp: En static member function `static int WATools::quality(const
char*)':
watools.cpp:80: error: `iw_sockets_close' undeclared (first use this function)
watools.cpp: En static member function `static int WATools::txpower(const
char*)':
watools.cpp:96: error: `iw_sockets_close' undeclared (first use this function)
watools.cpp: En static member function `static bool WATools::isWireless(const
char*)':
watools.cpp:112: error: `iw_sockets_close' undeclared (first use this function)
make[2]: *** [watools.o] Error 1
make[2]: *** Se espera a que terminen otras tareas....

see ya =)

Report

11 years ago

gnemmi

where it say "You should include ... This time I will do it for you." it should say "You should include sys/socket.h. This time I will do it for you."

for some reason the forum deleted it :s

see ya !

Report

11 years ago

pnawrocki

You need wireless-tools 27 for this to compile. If you are using version 26 or earlier (and it seems so) it should compile if you change all occurences of 'iw_sockets_close' with just 'close' in watools.cpp.
I'll make it work with older wireless-tools in the next release.

Report

11 years ago

gumby

I've just tried installing both CVS version and 0.5.3. Each fail just after the networks are detected just after starting. I found an older gentoo source, version 0.5.0, and it seems to be stable, is anyone else having these issues?

Report

11 years ago

pnawrocki

Hi.
There'll be a 0.5.4 release within days and it will include knoppix based debian packages. The creator of these packages reported no problems, so you might want to try them.
Thanks for the feedback.

Report

11 years ago

pnawrocki

Looks like it's not just your problem (2 posts up). Looks like I'll have to look into that anyway...

Report

11 years ago

gumby

I also had to use the suggestion of removing ifdown from the script. Otherwise the network card would not "come up" fast enough for the network test. I am using the package from here

http://gd.tuwien.ac.at/opsys/linux/gentoo/distfiles/wlassistant-0.5.0.tar.bz2

It compiles and works in debian sarge without any problem after I remove ifdown from the script. Maybe this will help in your troubleshooting

Report

11 years ago

gumby

Installed 0.5.4 tonight from source. I have the same crash issues. No reason given when started from a console. Here is the output including some from Kcrash...

terry@laptop terry]$ wlassistant
kdecore (KConfigSkeleton): Creating KConfigSkeleton (0x8145770)
kdecore (KConfigSkeleton): KConfigSkeleton::readConfig()
kdecore (KConfigSkeleton): KConfigSkeleton::readConfig()
Loaded application options.
Wireless interface(s): eth1
warning: /etc/resolv.conf not writable
Permissions checked.
DHCP Client: dhclient
All executables found.
Checking radio...
ok
ifup: /sbin/ifconfig eth1 up
scan: /sbin/iwlist eth1 scan
Networks found: 1
Checking for active connection.
Trying to get gateway address...
...from 'route'
Gateway address: 192.168.1.1
Active connection found.
Internet now accessible.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = wlassistant path = pid = 28098
kglobal_freeAll!!
[
0: /usr/lib/libkdecore.so.4(_Z11kdBacktracei+0x45) [0xb777b6a5]
1: /usr/lib/libkdecore.so.4(_Z11kdBacktracev+0x2b) [0xb777ba2b]
2: /usr/lib/libkdecore.so.4 [0xb781621f]
3: /usr/lib/libqt-mt.so.3(_ZN12QApplicationD2Ev+0x9b) [0xb710dabb]
4: /usr/lib/libkdecore.so.4(_ZN12KApplicationD1Ev+0x279) [0xb7769149]
5: drkonqi(_ZN7QWidget22windowActivationChangeEb+0x280) [0x8050718]
6: /lib/tls/libc.so.6(__libc_start_main+0xd0) [0xb6a71ec0]
7: drkonqi(_ZN7QWidget22windowActivationChangeEb+0x49) [0x80504e1]
]

Report

11 years ago

gumby

fresh install of wlassistant 5.4 on a fresh install of debian sarge. Tried both the source and the deb package. Same thing, network is detected and then wlassistant just disappears. anyone else having this issue or can offer a suggestion?

Report

11 years ago

gumby

one quick note, if I just open it as a user without sudo it doesnt crash, it sits at the screen that says I have insufficient permissions.... so its something after that at least. After I click ok I can see that it detects the card and ESSID of local networks but then again crashes.

Hopefully it is ok to post what the output is when running via command line....

terry@laptop:~/downloads/source/wlassistant-0.5.4a$ wlassistant
Loaded application options.
Wireless interface(s): eth1
warning: /etc/resolv.conf not writable
Permissions checked.
DHCP Client: dhclient
All executables found.
Checking radio...
ok
ifconfig_status: /sbin/ifconfig eth1
scan: /sbin/iwlist eth1 scan
Networks found: 1
Checking for active connection.
Trying to get gateway address...
...from 'route'
Gateway address: 192.168.1.1
Active connection found.
KCrash: Application 'wlassistant' crashing...

Gumby

Report

11 years ago

mkatl976

Which package works on Fedora Core 4. I dont which one to download/install.
Thanks

Report

Supporters

Recent Donations

Be the first to donate
Filename Version Description Filetype Packagetype License Downloads Date Filesize Install
Score 82%
82.00 Likes
18 Dislikes

0 Supporters for Wireless Assistant:

Recent Donations:

Be the first to donate
show all
Details
version
0.5.7
updated Apr 03 2007
added Mar 15 2005
downloads
page views 2262
support pnawrocki
For The Product
Wireless Assistant
5 - 10 - 25 - 50 - 100 - 200 - 500