kickdown
Unregistered
|
posted on 4/2/03 at 04:08
|
Hello!
If you experience problems using KWiFiManager, please
post them here. I'll try to help you if
possible.
Greetings,
Stefan Winter (KWiFiManager developer)
|
| |
| |
skaman
Newbie   Posts: 2 Registered: 19/5/04 Status: Offline |
posted on 19/5/04 at 16:01 |
While fairly comfortable with *nix environment, I have
not been successful getting kwifimanager to activate
a configuration. I am using SuSE 9.1 (latest
kernal) and a Linksys WPC54g wifi card via
ndiswrapper. When I click activate configuration, I
get the following error message:
Error for wireless request Set Encode (8B2A)
:
Invalid argument key
I would assume this error is generated by iwconfig
via the arguements passed by kwifimanger...???
The card works just fine if I setup the card
with a permanent ifcfg-wlan0 file with all parameters
in place (i.e., essid, key, etc.). However, this
is a pain to change for every hot spot that
I work in.
Any help would be greatly appreciated. |
| |
kickdown
Unregistered |
posted on 20/5/04 at 02:21 |
Hi!
> I would assume this error is generated by
iwconfig via the arguements passed by
> kwifimanger...???
Hm, there was an issue with the arguments some
(long) time ago. You are probably using KDE 3.2.2
(as shipped with SUSE 9.1), but still using
KWiFiManager 1.0.2. They still ship that old version
with their distro despite the fact that KWiFiManager
is included in KDE (kdenetwork) now. I suppose
your only option would be to compile the relevant
parts of kdenetwork yourself (that is, the
kdenetwork/wifi subdirectory). The newest version should
handle the key parameter correctly.
Greetings,
Stefan Winter |
| |
skaman
Newbie Posts: 2 Registered: 19/5/04 Status: Offline |
posted on 21/5/04 at 08:39 |
Hey Stefan,
I took your advice. I downloaded the latest CVS
tree for arts kdelibs and kdenetwork. I
recompiled and installed. Hmmm, same error message.
On a gamble, I installed an old Prism2 card
using the patched orinoco_cs driver to see if it
is a ndiswrapper problem. Got an error again
when clicking activate configuration ; however, this
time it says unknown commond ESSID with the
same error code.
To test the wireless-tools via the command line I
tried to start the card(s) using iwconfig and
passing the parameters for manual startup. Hmmmm,
same error messages occur.
Are you aware of any settings for iwconfig that
might prevent me from manually starting and
configuring my cards. They configure just fine
through the network card setup in YaST but not
manually. This could be my problem with
kwifimanager.
Regards,
Scott |
| |
kickdown
Unregistered |
posted on 22/5/04 at 01:45 |
> To test the wireless-tools via the command line
I tried to start the card(s) using
> iwconfig and passing the parameters for manual
startup. Hmmmm, same error
> messages occur.
Hmm, that sounds really odd. You did an ifconfig
ethX down before changing parameters like ESSID?
> Are you aware of any settings for iwconfig
that might prevent me from manually
> starting and configuring my cards. They
configure just fine through the network
> card setup in YaST but not manually. This
could be my problem with
> kwifimanager.
Well, you are probably right about that. Since
KWiFiManager essentially does the same things as
iwconfig does and not even iwconfig works, you seem
to have a problem somewhere near the kernel.
Unfortunately, I don?t have a clue whats happening
in SuSE 9.1. They used to use iwconfig for
setting up their stuff as well. The things you
talk about seem to imply they changed that (and,
probably, broke something).
I was going to install SuSE 9.1 anyway when it?s
available via FTP, so I will take a look at
it in the not-too-distant future.
If you find out something meanwhile, please let me
know.
Greetings,
Stefan Winter |
| |
opsman
Newbie Posts: 1 Registered: 2/7/04 Status: Offline |
posted on 2/7/04 at 14:44 |
I've installed Slackware 10.0 (KDE 3.2.3) and have
the same problem with kwifimanager as reported
earlier.
Error for wireless request Set Encode (8B2A)
:
Invalid argument key
- when activating a configuration which uses
encryption.
I don't get any errors using iwconfig to set the
key.
I'm using a D-Link DWL-AG650 with the madwifi
driver.
kwifimanager reports its version as verion 3.2.3
(KDE 3.2.3).
iwconfig reports its version as Version 26 -
compiled with WE v16
Any ideas why kwifimanager has a problem? |
| |
kickdown
Unregistered |
posted on 25/10/04 at 14:11 |
quote:
I've installed
Slackware 10.0 (KDE 3.2.3) and have the same
problem with kwifimanager as reported earlier.
Error for wireless request Set Encode (8B2A)
:
Invalid argument key
- when activating a configuration which uses
encryption.
I don't get any errors using iwconfig to set the
key.
I'm using a D-Link DWL-AG650 with the madwifi
driver.
kwifimanager reports its version as verion 3.2.3
(KDE 3.2.3).
iwconfig reports its version as Version 26 -
compiled with WE v16
Any ideas why kwifimanager has a problem?
Hi,
I have seen several occurences of this. First of
all, KWiFiManager IS using iwconfig to set the
parameters. But it uses one huge command line for
all parameters of the card, i.e.
iwconfig wlan0
Some cards seem to have timing problems with this
approach and so some of the arguments fail. This
sucks, because in theory the iwconfig command
is fine, the cards just can?t handle it.
Greetings,
Stefan Winter |
| |
