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=NOPASSW {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.Last changelog:
*** 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
Love your product. But I'm having trouble with the connection detection failing. Seems to be a recurring issue having read the thread. And I see that you rewrote that part in this last version. How can I ell what is really failing? Console was vague.
Always worked for me. When the distro supplied tool failed, it came to rescue.
Recently, Kubuntu 7.10 failed again (KNetworkManager never liked my laptops an d I never liked it). Wireless Assistant again did it.
Love it. Thanks pnawrocki.
Hi
I have an Acer Ferrari 3400 running FC7. I am pretty much a noobie, but I manged to install the lastest wl_apsta.o and bcm43xx-006. I also have installed wlassistant.
I am able to use wlassistant to scan the neighbourhood and see all the networks. I am able to connect with those that do not have any encription. I cannot connect to my LAN with has WEP. I have a Dlink router holding my lan together. The settings are open with a hex key. Windows connects without a problem, but FC7 will not connect. My router is listed in the scan and it correctly tells me it uses WEP.
My encription is 10-decimals. If I enter the decimals into Windows, it works, but not in FC7
Please forgive the typos...I am, after all, typomaster
typomaster
Hi. To troubleshoot your problem, you might do a few things. First of all, take a look at wlassistant console output (run it from console by typing 'sudo wlassistant' or 'kdesu wlassistant'). You can post it here, if you need more help with it. You can also try to connect manually using 'iwconfig' commands and 'dhcpcd' or 'dhclient' (don't know which one is present in FC). Let me know if that helped.
hi. the file is wlassistantrc. it's in the kde config directory (global or in your home directory), e.g. home/abc/.kde/share/config/.
"locate wlassistantrc" should give you the result.
I just upgraded to 0.5.7, but the WPA area is all grayed out and there are little question marks (?'s) next to each field including WPA provider.
What am I missing here??? Thanks.
Hi.
First, try to 'forget' current settings for the network, if it was configured before WPA was enabled on the access point, then try to connect with reconfiguring.
In case this doesn't work - make sure that "iwlist <iface> scan" returns WPA parameters for your network (post output if unsure).
Cheers
Hi there!
I have the same same problem questions marks for WPA... my adapter is a dwl-g122 versio b1, now if I do lsusb shows fine..so what are you suggesting is to the use ndiswrapper...
Hi. Wireless Assistant takes the values for WPA configuration from 'iwlist <iface> scan' output. If it's not there - there's not much I can do at the moment. The parsing will be replaced with iwlib calls, but that may take a while, even though I already started working on it. So if your driver does not report these values in iwlist output, by all means try ndiswrapper. Let me know if that helped.
I'm not capable of answering this question. You may however see this:
http://bugs.gentoo.org/show_bug.cgi?id=173313
to monitor the the progress. Cheers.
Hi. Wireless Assistant does not use Network Manager in any way. If you meant if it works simultaneously with Network Manager's management - I don't know, haven't tested. Hope that answers your question. Cheers.
Hi
I've install version 0.5.7 and it detects my WPA2 network as WEP. Why would it be doing this?
btw: I've never had any luck using wpa_supplicant to connect to my WPA2-PSK network. I've always had to use the iwpriv command. It seems to be more reliable.
Cheers
Dave
Hi. In case you had a different configuration before, chose "Forget Settings..." from the context menu of the WPA2 network, and reconfigure it. In case this does not help, please send me the output of your "iwlist <iface> scan" command (just the section with the WPA2 network).
Hi
This is the output of iwlist rausb0 scan
rausb0 Scan completed :
Cell 01 - Address: 00:14:7F:94:4E:90
ESSID:"BTHomeHub-B061"
Mode:Managed
Channel:1
Encryption key:on
Bit Rates:0 kb/s
Cheers
Hi. Judging from the output of your iwlist command, and this forum thread:
http://www.nabble.com/Re:-rt73-driver-trouble-t3523306.html
it's your wireless card driver that implements WPA in a non-standard way (not through Wireless Extensions). As suggested in the above-mentioned thread, it seems like choosing installing ndiswrapper and using the native windows driver is the best solution if you want to connect to a WPA-protected network. Let me know how that worked.
Hi
Thanks for your reply.
Sadly I can't use the native windows drivers as I run 64-bit Linux and Belkin never release 64-bit windows drivers.
Thanks anyway.
dave
{path_to_kde}/bin/wlassistant
Ratings & Comments
287 Comments
Love your product. But I'm having trouble with the connection detection failing. Seems to be a recurring issue having read the thread. And I see that you rewrote that part in this last version. How can I ell what is really failing? Console was vague.
Always worked for me. When the distro supplied tool failed, it came to rescue. Recently, Kubuntu 7.10 failed again (KNetworkManager never liked my laptops an d I never liked it). Wireless Assistant again did it. Love it. Thanks pnawrocki.
Cool. mine worked immediately :)
I have install the zenwalk linux and i want to know if this wireless assistant can work with them!!!
Hi, Keep getting this error with the new version scons: *** No tool named 'parser': not a Zip file What am I missing? Thanks!
Hi I have an Acer Ferrari 3400 running FC7. I am pretty much a noobie, but I manged to install the lastest wl_apsta.o and bcm43xx-006. I also have installed wlassistant. I am able to use wlassistant to scan the neighbourhood and see all the networks. I am able to connect with those that do not have any encription. I cannot connect to my LAN with has WEP. I have a Dlink router holding my lan together. The settings are open with a hex key. Windows connects without a problem, but FC7 will not connect. My router is listed in the scan and it correctly tells me it uses WEP. My encription is 10-decimals. If I enter the decimals into Windows, it works, but not in FC7 Please forgive the typos...I am, after all, typomaster typomaster
Hi. To troubleshoot your problem, you might do a few things. First of all, take a look at wlassistant console output (run it from console by typing 'sudo wlassistant' or 'kdesu wlassistant'). You can post it here, if you need more help with it. You can also try to connect manually using 'iwconfig' commands and 'dhcpcd' or 'dhclient' (don't know which one is present in FC). Let me know if that helped.
where is the config file for this program where it saves all the settings for wireless nets?
hi. the file is wlassistantrc. it's in the kde config directory (global or in your home directory), e.g. home/abc/.kde/share/config/. "locate wlassistantrc" should give you the result.
I just upgraded to 0.5.7, but the WPA area is all grayed out and there are little question marks (?'s) next to each field including WPA provider. What am I missing here??? Thanks.
Hi. First, try to 'forget' current settings for the network, if it was configured before WPA was enabled on the access point, then try to connect with reconfiguring. In case this doesn't work - make sure that "iwlist <iface> scan" returns WPA parameters for your network (post output if unsure). Cheers
Hi there! I have the same same problem questions marks for WPA... my adapter is a dwl-g122 versio b1, now if I do lsusb shows fine..so what are you suggesting is to the use ndiswrapper...
Hi. Wireless Assistant takes the values for WPA configuration from 'iwlist <iface> scan' output. If it's not there - there's not much I can do at the moment. The parsing will be replaced with iwlib calls, but that may take a while, even though I already started working on it. So if your driver does not report these values in iwlist output, by all means try ndiswrapper. Let me know if that helped.
Cool new version with wpa support available at http://3v1n0.tuxfamily.org/dists/edgy/3v1n0/ Bye!
Hi, when will this new version be available in gentoo?
I'm not capable of answering this question. You may however see this: http://bugs.gentoo.org/show_bug.cgi?id=173313 to monitor the the progress. Cheers.
Does this work with Network Manager?
Hi. Wireless Assistant does not use Network Manager in any way. If you meant if it works simultaneously with Network Manager's management - I don't know, haven't tested. Hope that answers your question. Cheers.
Hi I've install version 0.5.7 and it detects my WPA2 network as WEP. Why would it be doing this? btw: I've never had any luck using wpa_supplicant to connect to my WPA2-PSK network. I've always had to use the iwpriv command. It seems to be more reliable. Cheers Dave
Hi. In case you had a different configuration before, chose "Forget Settings..." from the context menu of the WPA2 network, and reconfigure it. In case this does not help, please send me the output of your "iwlist <iface> scan" command (just the section with the WPA2 network).
Thanks!
Hi This is the output of iwlist rausb0 scan rausb0 Scan completed : Cell 01 - Address: 00:14:7F:94:4E:90 ESSID:"BTHomeHub-B061" Mode:Managed Channel:1 Encryption key:on Bit Rates:0 kb/s Cheers
Hi. Judging from the output of your iwlist command, and this forum thread: http://www.nabble.com/Re:-rt73-driver-trouble-t3523306.html it's your wireless card driver that implements WPA in a non-standard way (not through Wireless Extensions). As suggested in the above-mentioned thread, it seems like choosing installing ndiswrapper and using the native windows driver is the best solution if you want to connect to a WPA-protected network. Let me know how that worked.
Hi Thanks for your reply. Sadly I can't use the native windows drivers as I run 64-bit Linux and Belkin never release 64-bit windows drivers. Thanks anyway. dave
I was having difficulties in setting up my wireless on my laptop with out of the box tools. None worked. This one worked like a gem.