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

9 years ago

pnawrocki

Thanks!

Report

9 years ago

dzamboun

Hi. I like you application very much and WPA support is very good news! After try your last version i have problems with the table (list of APs) size, which is bigger the window area and a horizontal scrollbar appears. I have changed columns size to solve that, but after click on the "Refresh" button was problem back :(.

Report

9 years ago

pnawrocki

Hi, Thanks for your comment!
It's like that by design, so the AP is not immediately visible, as it's needed only on very rare occasions and would add to complexity/clutter. It has been like that since 0.5.0.

Report

10 years ago

robohead44

I am glad to hear that we will get WPA support soon! Your tool really helps as its the only reliable Linux-GUI for Wifi that I have come accross so far.

I was just wondering whether you might want to consider a tighter integration of your tool into KDE 4. It seems like KDE's standard wifi support is weak out of the box and that wlassistant should really become a standard component for wifi-network usage under KDE.

In particular I wonder whether you should consider coordinating your efforts with the guys who are working on the Solid Library (the new Hardware Abstraction API for KDE4). They already seem to have started on a Wifi-API as can be seen here: http://api.kde.org/cvs-api/kdelibs-apidocs/solid/html/classSolid_1_1Ifaces_1_1WirelessNetwork.html

I think if you split your wlassistant into backend/frontend for integration into Solid / Plasma respectively then that would really add to the overall KDE4 result!

Either way, keep up the great work!

Report

9 years ago

pnawrocki

Hi,
Thank you for your comments!
For your idea to come true, I first need to separate wlassistant into lib and frontend (as you suggested) AND port it to Qt4, which I don't really have time for, as of now and upcoming months. There exists a rewrite in Qt4 at _very_ early stages of development, but I had to stop working on it due to lack of time. So, as soon as I manage to start the porting, I will get back to your idea. It doesn't seem feasible earlier. Thanks.

Report

10 years ago

maximusmagni

I do not think you realize how important WPA is. At the university I go to everything is WPA because we realize that WEP is useless. Where I am, not supporting WPA is just as good as not supporting wireless at all.

Report

10 years ago

pnawrocki

I do realize that. There's already experimental WPA-PSK support in my local copy, so wait a bit for the next release. Thanks for your comment!

Report

10 years ago

cjpedersen

I recently upgraded wlassistant from Fedora Core repositories (update created 18 Jan, installed 20 Jan). Ever since, I have unable to successfully connect to APs running a dhcp server. The problem doesn't appear to be the dhcp client software. It hasn't been upgraded since before my last wlassistant update when everything was working fine. Also, if after wlassistant has returned connection failed, I invoke 'dhclient eth0', I get a a good connection straight away. Wlassistant binds the proper AP and enc values to the interface, but there seems to be some problem in how dhclient is invoked. I tried increasing the timeout but this had no effect. When I invoke dhclient by hand, it binds is about half the timeout interval I set in wlassisnt.

Report

10 years ago

pnawrocki

That's a known problem and I'll do my best to solve it in the next release. Thanks for your comment!

Report

10 years ago

cjpedersen

OK, good answer. Happy to beta test on a thinkpad t60p running FC 6 if it would help. Just drop me a line: charles.pedersen [at] sri.com

Report

10 years ago

vietnam2007

I had no problem with version 0.5.5. While update to version 0.5.6 I got connection failed... please help.

Report

10 years ago

pnawrocki

please email me your console output. thx.

Report

10 years ago

vietnam2007

Thanks, below is the /var/log/messeges, again after reinstall 0.5.5 everything work fine. Many Thanks!

Feb 10 14:31:42 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.2
Feb 10 14:31:42 localhost dhclient: Copyright 2004 Internet Systems Consortium.
Feb 10 14:31:42 localhost dhclient: All rights reserved.
Feb 10 14:31:42 localhost dhclient: For info, please visit http://www.isc.org/products/DHCP
Feb 10 14:31:42 localhost dhclient:
Feb 10 14:31:42 localhost dhclient: Listening on LPF/eth1/00:13:ce:88:f7:09
Feb 10 14:31:42 localhost dhclient: Sending on LPF/eth1/00:13:ce:88:f7:09
Feb 10 14:31:42 localhost dhclient: Sending on Socket/fallback
Feb 10 14:31:42 localhost dhclient: DHCPRELEASE on eth1 to 192.168.1.1 port 67
Feb 10 14:31:42 localhost dhclient: send_packet: Network is unreachable
Feb 10 14:31:42 localhost dhclient: send_packet: please consult README file regarding broadcast address.
Feb 10 14:31:42 localhost kernel: bridge-eth1: is a Wireless Adapter
Feb 10 14:31:42 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.2
Feb 10 14:31:42 localhost dhclient: Copyright 2004 Internet Systems Consortium.
Feb 10 14:31:42 localhost dhclient: All rights reserved.
Feb 10 14:31:42 localhost dhclient: For info, please visit http://www.isc.org/products/DHCP
Feb 10 14:31:42 localhost dhclient:
Feb 10 14:31:42 localhost kernel: bridge-eth1: is a Wireless Adapter
Feb 10 14:31:43 localhost dhclient: Listening on LPF/eth1/00:13:ce:88:f7:09
Feb 10 14:31:43 localhost dhclient: Sending on LPF/eth1/00:13:ce:88:f7:09
Feb 10 14:31:43 localhost dhclient: Sending on Socket/fallback
Feb 10 14:31:44 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
Feb 10 14:31:45 localhost dhclient: DHCPOFFER from 192.168.1.1
Feb 10 14:31:45 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
Feb 10 14:31:47 localhost dhclient: DHCPACK from 192.168.1.1
Feb 10 14:31:47 localhost NET[6986]: /sbin/dhclient-script : updated /etc/resolv.conf
Feb 10 14:31:47 localhost dhclient: bound to 192.168.1.114 -- renewal in 33295 seconds.
Feb 10 14:31:47 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.2
Feb 10 14:31:47 localhost dhclient: Copyright 2004 Internet Systems Consortium.
Feb 10 14:31:47 localhost dhclient: All rights reserved.
Feb 10 14:31:47 localhost dhclient: For info, please visit http://www.isc.org/products/DHCP
Feb 10 14:31:47 localhost dhclient:
Feb 10 14:31:47 localhost dhclient: Listening on LPF/eth1/00:13:ce:88:f7:09
Feb 10 14:31:47 localhost dhclient: Sending on LPF/eth1/00:13:ce:88:f7:09
Feb 10 14:31:47 localhost dhclient: Sending on Socket/fallback
Feb 10 14:31:47 localhost dhclient: DHCPRELEASE on eth1 to 192.168.1.1 port 67
Feb 10 14:31:47 localhost NET[7020]: /sbin/dhclient-script : updated /etc/resolv.conf

Report

10 years ago

pnawrocki

ok, this looks like a repeating problem. I'll look into that and it should be fixed with the next release to come soon. thx!

Report

10 years ago

easuter

Will Wireless Assistant include WPA/WPA support in the near future?

Great app otherwise!

Report

10 years ago

pnawrocki

thanks! sooner rather than later. as for now, you can try using the pre/post connection commands in the advanced tab of connection settings to run wpa_supplicant. feedback is always welcome!

Report

10 years ago

Arabian

Great app.

Could you please make a port for FreeBSD?

Report

10 years ago

polrus

I have 2 networks in my range. One regular WEP encrypted in Managed mode and another laptop with Ad-Hoc mode with WEP in ASCII.
Wireless Assistant doesnt' list ad-hoc WEP network that commend 'awlist ath0 scan' shows.

Report

10 years ago

pnawrocki

Ad-Hoc was disabled at some point, as it didn't really work. Should be redone in 0.5.6 release but I didn't find the time to do it. It's on the TODO list for next version. Contact me at my email if you wish to help or test at a later time. Thanks for your comment.

Report

10 years ago

polrus

ok I sent You the fix by email

Report

10 years ago

Divilinux

now is perfect..tnx

Report

10 years ago

Divilinux

some problems with edgy 6.10..
build/src/watools.h:21:19: error: iwlib.h: No such file or directory
build/src/watools.cpp: In static member function 'static char* WATools::ap(const char*)':
build/src/watools.cpp:36: error: 'iw_sockets_open' was not declared in this scope
build/src/watools.cpp:40: error: aggregate 'iwreq req' has incomplete type and cannot be defined
build/src/watools.cpp:41: error: 'SIOCGIWAP' was not declared in this scope
build/src/watools.cpp:41: error: 'iw_get_ext' was not declared in this scope
build/src/watools.cpp:44: error: 'iw_ether_ntop' was not declared in this scope
build/src/watools.cpp: In static member function 'static int WATools::quality(const char*)':
build/src/watools.cpp:54: error: 'iw_range' was not declared in this scope
build/src/watools.cpp:54: error: expected `;' before 'range'
build/src/watools.cpp:55: error: 'iw_statistics' was not declared in this scope
build/src/watools.cpp:55: error: expected `;' before 'stats'
build/src/watools.cpp:58: error: 'iw_sockets_open' was not declared in this scope
build/src/watools.cpp:62: error: 'range' was not declared in this scope
build/src/watools.cpp:62: error: 'iw_get_range_info' was not declared in this scope
build/src/watools.cpp:67: error: 'stats' was not declared in this scope
build/src/watools.cpp:67: error: 'range' was not declared in this scope
build/src/watools.cpp:67: error: 'iw_get_stats' was not declared in this scope
build/src/watools.cpp: In static member function 'static int WATools::txpower(const char*)':
build/src/watools.cpp:80: error: 'iw_sockets_open' was not declared in this scope
build/src/watools.cpp:85: error: aggregate 'iwreq req' has incomplete type and cannot be defined
build/src/watools.cpp:86: error: 'SIOCGIWTXPOW' was not declared in this scope
build/src/watools.cpp:86: error: 'iw_get_ext' was not declared in this scope
build/src/watools.cpp: In static member function 'static bool WATools::isWireless(const char*)':
build/src/watools.cpp:99: error: 'iw_sockets_open' was not declared in this scope
build/src/watools.cpp:104: error: aggregate 'iwreq req' has incomplete type and cannot be defined
build/src/watools.cpp:105: error: 'SIOCGIWNAME' was not declared in this scope
build/src/watools.cpp:105: error: 'iw_get_ext' was not declared in this scope
build/src/watools.cpp: In static member function 'static void WATools::cleanup()':
build/src/watools.cpp:114: error: 'iw_sockets_close' was not declared in this scope
scons: *** [build/src/watools.o] Error 1
scons: building terminated because of errors.
make: *** [all] Error 2


Report

10 years ago

ach

Look at the first line of the errors.
you miss iwlib.h.

sudo aptitude install libiw-dev

installs the file.

FWIW: you can check build dependencies
of pkgs with:

$ apt-cache showsrc wlassistant | grep -i build-dep
Build-Depends: debhelper (>= 5.0), scons, cdbs, kdelibs4-dev, net-tools, wireless-tools, libiw-dev, librsvg2-bin

you need to uncomment the deb-src lines
in sources.list to get 'showrc' data.

Achim

Report

10 years ago

katakombi

Hi,

I found that wlassistant dumps the WEP key as debugging output.
Maybe that's a security problem?

Report

10 years ago

pnawrocki

Thanks for pointing this out. That reminded me, that the key is also visible in the connection properties edit dialog. Will fix.
Cheers.

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 2276
support pnawrocki
For The Product
Wireless Assistant
5 - 10 - 25 - 50 - 100 - 200 - 500