Failed to initialize interface 'wlan0'

[GoogleCodeExporter]

What steps will reproduce the problem?
1. executing reaver with given example usage
2.
3.

What is the expected output? What do you see instead?

Does not work with my driver apparently...

[-] Failed to initialize interface 'wlan0'
[-] Failed to recover WPA key

What version of the product are you using? On what operating system?

reaver v1.1
3.1.5 Kernel
ArchLinux x86_64

Please provide any additional information below.

Have tried both iwconfig and airmon-ng and verified my card is in monitor mode 
and ready for action but no love... I know my card supports injection etc. but 
for some odd reason reaver doesn't like it.

Original issue reported on code.google.com by sherrod...@gmail.com on 30 Dec 2011 at 7:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Try using mon0 as interface, airmon-ng will tell you what the correct interface 
is.

after you do airmon-ng start wlan0, it will create mon0 for usage.

Original comment by stefanen...@gmail.com on 30 Dec 2011 at 10:30

[GoogleCodeExporter]

Yes, you need to specify the monitor mode interface and also ensure that reaver 
is running as root.

Original comment by cheff...@tacnetsol.com on 30 Dec 2011 at 2:27

• Changed state: Invalid

[GoogleCodeExporter]

Yes, thanks for the suggestions. I have tried both mon0 and wlan0 both in 
monitor mode ofc. Both to no avail. Perhaps this card is not supported?

Original comment by sherrod...@gmail.com on 30 Dec 2011 at 6:24

[GoogleCodeExporter]

I will try running reaver as root as I don't think I have tried that yet and 
report back later today. Thanks.

-Steve

Original comment by sherrod...@gmail.com on 30 Dec 2011 at 6:25

[GoogleCodeExporter]

So 1.2 seems to work fine (as root using mon0 via airmon-ng). Still fails with 
v1.1 both as root or normal user.

Original comment by sherrod...@gmail.com on 31 Dec 2011 at 3:46

[GoogleCodeExporter]

Not sure what exactly the issue is with 1.1, but it's likely related to the 
struct packing bug which was the cause of several issues. This was fixed in 
release 1.2.

Original comment by cheff...@tacnetsol.com on 31 Dec 2011 at 4:45