Error for wireless request "Set Mode" (8B06)

[andyem]

Just finished getting the wep key from aircrack but I keep seeing this error when I try to use the key.

I have tried the following commands:

# iwconfig ath0 mode managed key 40:EF:CC:26:34
Error for wireless request "Set Mode" (8B06) :
SET failed on device ath0 ; Invalid argument.

Then I tried destroying the ath0 thinking that might be the problem:
# wlanconfig ath0 destroy

# iwconfig wifi0 mode managed key 40:EF:CC:26:34
Error for wireless request "Set Mode" (8B06) :
SET failed on device wifi0 ; Invalid argument.

Same issue.

# iwconfig
lo no wireless extensions.

wifi0 no wireless extensions.

eth0 no wireless extensions.

I searched google but everyone claims its a driver issue and I know thats not the reason because I am able to connect to OPN ap's without a problem. I searched this forum but this question has not been answered.

Any ideas?

[theprez98]

# iwconfig ath0 mode managed key 40:EF:CC:26:34

Remove the :'s and try again. Also, try without setting the mode.

[andyem]

Remove the :'s and try again. Also, try without setting the mode.

# iwconfig wifi0 key 40EFCC2634
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wifi0 ; Invalid argument.

it produced the encode error.

I even get similar results with:

# iwconfig wifi0 mode managed key 40EFCC2634
Error for wireless request "Set Mode" (8B06) :
SET failed on device wifi0 ; Invalid argument.

Then I tried to enable mon mode and run it off of ath0 but:

# airmon-ng start wifi0


Interface Chipset Driver

wifi0 Atheros madwifi-ng
ath0 Atheros madwifi-ng VAP (parent: wifi0) (monitor mode enabled)

# iwconfig ath0 mode managed key 40EFCC2634
Error for wireless request "Set Mode" (8B06) :
SET failed on device ath0 ; Invalid argument.

THIS WORKED: # iwconfig ath0 key 40EFCC2634

[theprez98]

THIS WORKED: # iwconfig ath0 key 40EFCC2634

There you go.

[andyem]

There you go.

Thx for the help. I really wanted to post the results because I hate when threads go unfinished especially when its exactly the same problem I have

[theprez98]

Thx for the help. I really wanted to post the results because I hate when threads go unfinished especially when its exactly the same problem I have

Believe me, we appreciate that. Someone else will inevitably come along with the same problem. If we can educate users enough to use the search feature (yes, its a long process to get there), then someone will find your thread and learn something new without having to post a new thread.

[andyem]

Believe me, we appreciate that. Someone else will inevitably come along with the same problem. If we can educate users enough to use the search feature (yes, its a long process to get there), then someone will find your thread and learn something new without having to post a new thread.

I'll always put the exact error in the title making even that much easier to find

[shamanvirtuel]

yes it's a good thing to put exact pb in title....will shorten the time of seeking for ppls who have the same pb

BTW prez i begin build a kind of leetmode with a fonction for searching in this forum....in the wiki....and into google...

will be a good thing...i also begin a kind of(don't laugh pliz) "BackTrack 4 Dummies" manual....with all basic procedures........

Best Regards....

[andyem]

yes it's a good thing to put exact pb in title....will shorten the time of seeking for ppls who have the same pb

BTW prez i begin build a kind of leetmode with a fonction for searching in this forum....in the wiki....and into google...

will be a good thing...i also begin a kind of(don't laugh pliz) "BackTrack 4 Dummies" manual....with all basic procedures........

Best Regards....

Hey no laughing here, I'll surely be reading it

[shamanvirtuel]

even for "experimented" users .... it's not a bad thing to have all basic procedures in a clear document....will be i think a pdf ebook....

i just begin so ..... you may wait a long time....