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

polemos

It works successfully with kernel 2.6.14

But now i'm running 2.6.14.2.No work :(

Report

11 years ago

polemos

The problem is killing dhcpd.No problem about timeout.

Report

11 years ago

pnawrocki

Hi. Could you specify it a little more? Thx.

Report

11 years ago

polemos

dhcpcd.log :

Nov 21 08:57:32 mella dhcpcd[18912]: broadcasting DHCP_DISCOVER
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpIPaddrLeaseTime=86400 in DHCP server response.
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
Nov 21 08:57:32 mella dhcpcd[18912]: DHCP_OFFER received from ÿ (10.0.0.2)
Nov 21 08:57:32 mella dhcpcd[18912]: broadcasting DHCP_REQUEST for 10.0.0.11
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpIPaddrLeaseTime=86400 in DHCP server response.
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
Nov 21 08:57:32 mella dhcpcd[18912]: DHCP_NAK server response received
Nov 21 08:57:32 mella dhcpcd[18912]: broadcasting DHCP_DISCOVER
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpIPaddrLeaseTime=86400 in DHCP server response.
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
Nov 21 08:57:32 mella dhcpcd[18912]: DHCP_OFFER received from ÿ (10.0.0.2)
Nov 21 08:57:32 mella dhcpcd[18912]: broadcasting DHCP_REQUEST for 10.0.0.11
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpIPaddrLeaseTime=86400 in DHCP server response.
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
Nov 21 08:57:32 mella dhcpcd[18912]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
Nov 21 08:57:32 mella dhcpcd[18912]: DHCP_ACK received from ÿ (10.0.0.2)
Nov 21 08:57:33 mella dhcpcd[18916]: terminating on signal 13

wlassistant console output :

ifup: /sbin/ifconfig eth0 up
iwconfig_set: /usr/sbin/iwconfig eth0 essid Slackware mode managed channel 6 key open 3B5D3C7D207E37DCEEEDD301E3
iwconfig_ap: /usr/sbin/iwconfig eth0 ap 00:11:D8:2A:EF:26
ifconfig_dhcp: /sbin/dhcpcd -nd eth0
Checking for active connection.
Checking for active connection.
Checking for active connection.
Checking for active connection.
Checking for active connection.
Checking for active connection.
Checking for active connection.
Checking for active connection.
Checking for active connection.

after all dhcpcd looks working with ps aux !

root 18917 0.0 0.0 1500 216 ? Ss 08:57 0:00 /sbin/dhcpcd -nd eth0

Slackware 10.2,Linux 2.6.14.2

Thanks

Report

11 years ago

animefan

Hi,

there is already a very mighty and great application like that for the GnomeDesktop : NetworkManager, it uses DBUS, HAL and several backends to provide a real great usability experience. As it is very modular and they already thought of a way enabling more GUIs, why not create a KDE fronted for it, when you make the next version?!

Report

11 years ago

polemos

What about to make this app all-in-one,

- sits on sys tray with signal strength icon
- wl power management
- bring up/down iface

Thanks for the good app.That makes my life easier :)

Report

11 years ago

pnawrocki

I'm already working on a Qt4 based rewrite of wlassistant which will support monitoring and all the fancy features many users wished for. It will be a totally redesigned application, so extending its functionality won't be as much of a pain as it is with the current version. It's just not designed well and was written without a precise plan.
This also means that I don't think I'll have the time to add any significant features to the KDE 3.x wlassistant though, most likely just bug fixes and small improvements.
Stay tuned and in some time you will see the best wlassistant ever ;)
Cheers,
Pawel.

Report

11 years ago

bushwakko

that should really include wpa_supplicant integration instead (or is it perhaps wpa_cli ?) since it really rocks... If you haven't tried it yo ureally should. ;)

Report

11 years ago

jirityr

# Copyright 1999-2004 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

inherit kde

#S=${WORKDIR}/maxemumtvguide-${PV}

DESCRIPTION="Wireless Assistant is a small application that allows you to connect to wireless networks."
HOMEPAGE="http://wlassistant.sourceforge.net/"
SRC_URI="mirror://sourceforge/wlassistant/${P}.tar.bz2"
LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

RDEPEND="net-misc/dhcpcd
>=net-wireless/wireless-tools-27
app-admin/sudo"

need-kde 3.4

Report

11 years ago

jaykayess

This is so much better than kwifimanager. I also agree that it could use a system tray, however.

About kdesu-- change the .desktop file to use "kdesu wlassistant"-- they way you have it now will fail silently unless the user has sudo setup to skip password checks, which not everyone does. (It took me a few minutes to figure out why I couldn't launch...)

Report

11 years ago

bushwakko

I have a few suggestions:

- you should make it integrate with kde's sudo and have an option for remember password.

- you could make an systray icon (have you ever seen apple's airport? its great)

- you should make it integrate with wpa_supplicant or even better wpa_supplicants libs if any. wpa supplicant allready works with wep and different wpas and such, it also runs as a deamon and supports priority and stuff

just a few ideas! ;)

fantastic work

Report

11 years ago

fwarren

A problem I have had with all wireless apps except for "WiFi Mananger" has been you can not use a "restricted key"

For Encryption types, could you have, "Shared Key" "Open" and "Restricted Key"

Report

11 years ago

pnawrocki

Hi!
"Restricted" is a wireless-tools name that is equivalent with "Shared Key" (as opposed to "Open")
So, if you want 'restricted' use 'shared'. It's the same thing.
Cheers.

Report

11 years ago

robbeh

Unfortunately this app messes up my wireless configuration after using it. The antenna is switched off, the driver-module is unloaded and the card isn`t recognized, even after reloading the driver manually. Have to restart linux, then everything works fine. Same on two systems.
I use the rt2500 module, compiled against 2.6.7, KDE 3.4.

Sorry, but I can`t recommend this app.

Report

11 years ago

Heart

Hi,

I installed your app successfully and when I start it in a console I get these lines:

Checking radio...
ok
ifconfig_status: /sbin/ifconfig wlan0
scan: /sbin/iwlist wlan0 scan
==>stderr: wlan0 Interface doesn't support scanning : Function not implemented

No networks found!

I'm using Draytek's Vigor 510 (USB) for my wlan.

What does above error means exactly? My usb dongle doesn't support scanning for AP's so Wireless Assistant is then useless for me :(!?

Thanks

Report

11 years ago

sheldonl

To the developer(s). Thank you very much for this program. It has definately made my life much much easier. I setup my stuff and have absolutely no problems! You guys rock!

Report

11 years ago

gumby

I've installed 5.4a on both debian and mandrake systems. Both do the exact same thing. The program opens, it sees an AP, and the crashes immediately. Has there been any update as to why this might be? It happens with both compiled and precompiled versions. I've made sure each time to delete any files related to wlassistant before each install.

Gumby

Report

11 years ago

pnawrocki

Hi!
I am aware that this problem has not been fixed yet. Even though I tried, I could not reproduce this crash even once... in that case, fixing this is totally dependant on the users' (like you;) feedback and debugger/console/other outputs they send me. Any help is appreciated and I won't be able to fix this without it.
Cheers.
PS: If you feel like helping out, feel free to write to my email.

Report

11 years ago

kilgoretrout

Scanning works fine, but when I try to connect to anything, I get "ERROR: Couldn't obtain an IP address!". I've set my dhcpcd path to "/sbin/dhclient", which exists and I thought works okay. Can anyone point me in the right direction? thanks.

Report

11 years ago

pnawrocki

Hi!
1st: you do not set the path do dhclient - it's detected automatically (look at console output for detected DHCP client). The things you do set in the config file are path to .pid file and path to file with lease information (read only purposes).
If you have problems obtaining an IP address via DHCP, try increasing the DHCP client timeout in the options.
If you still have problems - what does console output say? Does it work if you run dhclient manually from the console?
Hope that helps.

Report

11 years ago

pnawrocki

Oh. Actually it seems like you're using a very old wlassistant version (0.3.x). The above post assumes you are using at least 0.5.0. I do recommend that you download the 0.5.4. Good luck.

Report

11 years ago

bushwakko

sudo doesn't work for me, says:

wakko@lapwakko ~ $ sudo wlassistant
wlassistant: cannot connect to X server

if I drop the sudo it works, but it's limited because of the user. suing and then running as root works. I think you should use the kdesu thing that most kde-apps that need root-access use. You can even remeber that it has root access and it will just start the next time I think, I know systray apps do that (And the should REALLY be a systray app)

btw: FANTASTIC APP :D

Report

11 years ago

jmack1010

I had the same problem, so I just do a runas root in the kmenu for the time being.

Report

11 years ago

bushwakko

I didn't like the pinging of google.com, It's not a very good way to check for a network connection, if dhcp is given that should suffice. We have a network on campus which when you connect to it you only get dhcp, and you when you first open ANY website, you get to an authentication page, and THEN you get access to google. Pinging to check if the network is connected is redundant and unneccesary. If you get dhcp, you are authed correctly :)

Report

11 years ago

pnawrocki

Hi. Pniging some host on the internet is useful in some cases. Getting a dhcp lease means only that you were connected to the access point. If you're connected to AP but it has some problems or you need to login via a webpage before accessing network - you might want to know whether internet is yet accessible or not. That's why wlassistant since 0.5.4 has 3 different connection states: not connected, connected to AP and connected to internet.

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