
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
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.
13 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
13 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
kakadoli
14 years ago
I hope therefore that somebody helped me.
I know the method to do only the decompression.
thx for reading the text at me.
Report
andrelewis
14 years ago
Just want to confirm
Gentoo port of wlassistant sees wireless, allows me to configure it, etc.
It appears as if wlassistant runs the wrong dhcp command which should normally allow dhcpcd to find the correct router information. Dhcp works correctly as issuing the '/sbin/dhcpcd wlan0' comand from the command prompt works perfectly.
wlassistant shows the following at the console:
>ifup: /sbin/ifconfig wlan0 up
>iwconfig_ap: /sbin/iwconfig wlan0 ap 00:0c:41:BE:7A:23
>ifconfig_dhcp: /sbin/dhcpcd -nd wlan0()
Trying to get gateway address...
...from 'route'
No default gateway.
Checking for active connection.
No default gateway.
Report
timcharper
14 years ago
I've posted here before. Recently, wlassistant often wont pull the gateway address for the wireless router, and I have to manually set it via
ip route add default via (gateway-address) dev wlan0
Does anyone know why this happens? Is there a fix?
Report
tmichel
14 years ago
If you start kwlan from a terminal session (either with sudo or root as it needs permissions for configuring the interface) you can see the output of dhclient. Maybe it can give you a hint.
Report
timcharper
14 years ago
I'm gonna have to debug dhclient to see why it's behaving so badly.
Report
timcharper
14 years ago
I switched to Suse Linux 10.1, and the problem went away.
Report
brockers
14 years ago
Bobby
Report
ach
14 years ago
You can add wlassitant icon
next to the systray without problem.
While not in the systray at least next
to it ;)
Maybe have a look at
ksystraycmd --help
Achim
Report
gohanz
15 years ago
http://www.slacky.it/
http://www.slacky.it/index.php?option=com_remository&Itemid=1&func=fileinfo&filecatid=956&parent=category
Report
loenen
15 years ago
Any idea?
Report
pnawrocki
15 years ago
Could you please post this question together with the console output on the public forums (homepage link above)? it will be easier to hunt the problem down there. And please specify what wireless card and kernel module for it are you using. Thanks in advance!
Report
timcharper
14 years ago
I just thought I'd let you know this bug seems to be more network specific. At my work office, we have a WEP encrypted wireless network. From here I can connect without any trouble at all, and it doesn't report that the connection failed.
if you need any more info, feel free to contact me timcharper at gmail dot com.
Report
pnawrocki
14 years ago
Actually, it's something I CAN reproduce and will definitely look into that. Cheers.
Report
timcharper
14 years ago
Report
timcharper
14 years ago
lease {
interface "wlan0";
fixed-address 10.4.76.193;
option subnet-mask 255.255.254.0;
option dhcp-lease-time 14400;
option routers 10.4.76.1;
option dhcp-message-type 5;
option domain-name-servers 128.187.22.202,128.187.22.129;
option dhcp-server-identifier 10.8.0.2;
option domain-name "app.byu.edu";
renew 1 2006/3/13 19:56:03;
rebind 1 2006/3/13 19:56:03;
expire 1 2006/3/13 19:56:03;
}
lease {
interface "wlan0";
fixed-address 10.4.76.193;
option subnet-mask 255.255.254.0;
option dhcp-lease-time 14400;
option routers 10.4.76.1;
option dhcp-message-type 5;
option domain-name-servers 128.187.22.202,128.187.22.129;
option dhcp-server-identifier 10.8.0.2;
option domain-name "app.byu.edu";
renew 1 2006/3/13 21:29:56;
rebind 1 2006/3/13 23:26:05;
expire 1 2006/3/13 23:56:05;
}
hope that might be of some assistance. thank you so much, this is a marvelous tool!
Tim
Report
timcharper
14 years ago
Note, I'm posting this information on the connection created by wlassistant, which was reported as failed, but is infact working.
Here's the console output I'm getting:
Loaded application options.
DHCP Client: dhclient
All executables found.
iwconfig_status: /sbin/iwconfig
==>stderr: lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
Wireless interface(s): wlan0
Permissions checked.
ifconfig_status: /sbin/ifconfig wlan0
ifup: /sbin/ifconfig wlan0 up
scan: /sbin/iwlist wlan0 scan
Networks found: 7
Checking for active connection.
Trying to get gateway address...
...from /var/lib/dhcp/dhclient.leases
Gateway address: 10.4.76.1
==>stderr: connect: No such device
ACTION: CONNECT.
kill_dhcp: /sbin/dhclient -r wlan0
==>stderr: Internet Systems Consortium DHCP Client V3.0.2-RedHat
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on LPF/wlan0/00:90:4b:db:aa:47
Sending on LPF/wlan0/00:90:4b:db:aa:47
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 10.8.0.2 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ifup: /sbin/ifconfig wlan0 up
iwconfig_set: /sbin/iwconfig wlan0 mode managed channel 1 key off essid byuc0ug4rs
iwconfig_ap: /sbin/iwconfig wlan0 ap 00:0F:24:20:83:20
ifconfig_dhcp: /sbin/dhclient -q wlan0
Checking for active connection.
Checking for active connection.
-------------------
My school does not do WEP encryption, nor VPN. It authorizes clients by their mac address, and redirects all http requests for unauthorized mac addresses to a webpage prompting them to log in. The connection reports failed in wlassistant, even though I've already been authorized on the network from a previous connection (my school only prompts me once a day)
Additionally, here is my routing table information (for my allegedly failed connection) :
10.4.76.0/23 dev wlan0 proto kernel scope link src 10.4.76.193
default via 10.4.76.1 dev wlan0
My network card is a Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller. I'm using the windows drivers for it via ndiswrapper.
Thank you,
Tim
Report
GreatBunzinni
15 years ago
Are there any plans to create a kubuntu package? That would really come in handy.
Report
ach
15 years ago
there are problem with connect/
disconnect and so uploading is
on hold.
For debian and kubuntu pkgs see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322874
and for TODOs
http://svn.debian.org/wsvn/pkg-kde/kde-extras/wlassistant/trunk/debian/TODO?op=file&rev=0&sc=0
Achim
Report
awbacker
15 years ago
Didn't realize about it needing root, so remember to edit it's menu item in the kmenu if you plan to launch it from there, or follow the help in the description. I found out by launching it from a root console.
Not sure how I'll reconcile this with the startup routine, and it would be nice to maintain a list of 'known' networks for where I commonly go, but that's not essential.
Thanks!
Report
chrisdog
15 years ago
but really great when you are not at home and want to check you mail through a public wavelan, great work :)
Report
keba
15 years ago
Report
Paloseco
15 years ago
http://www.udc.es/udcwifi/configuracion.htm
Report
pnawrocki
15 years ago
the qt4 rewritten/overhauled program i'm working on will support WPA. At first only by calling the wpa_gui (part of wpa_supplicant). Depending on how well/poorly this will work, it might be changed in the far future.
Cheers,
Pawel
Report
angrymob
15 years ago
Report
neogeek77
15 years ago
however, when i log in as a non-root user, i cannot load the application. the wireless connection keeps getting d/c when i cannot connect to my wireless network using the "wireless assistant".
info: using fedore core 4.
thanks!
Report