Reaver getting all info but no pin about reaver-wps-fork-t6x

[JaviStealsLions]

This is how I ended up cracking my WiFi: Used command reaver -i wlan0mon -b XX:XX:XX:XX:XX:XX(BSSID) -c # -vvv

If prompted with error associating use aireplay-ng --fakeauth 1 -a XX:XX:XX:XX:XX:XX(BSSID) -h XX:XX:XX:XX:XX:XX(MAC of interface) wlan0mon in a different Terminal.

Use wash -i wlan0mon in another Terminal to determine signal strength. That was my main problem. I was operating at -79ish, and when I grabbed a USB male to female and extended its reach from my PC I now have a signal of -62

The crack took 2 hours and 30 minutes long to complete.

I did get a bunch of WPS transaction failed (code: 0x03), re-trying last pin's throughout so don't worry like I was

Hope this helps someone! :)

[d8tahead]

It seems to be an older version. The new versions require -vvv instead of -vv. try and update to the latest version of reaver and also, in case, pixiewps.

You can also try without -S, and you might get a different pixiewps result. I can't verify if you will or not, as I have not looked up the router model for its chipset.

[thesolyom]

Both were updated to the latest version and I used t6x version of reaver. and also kali 2. Am I correct in thinking that pixiewps might not get the pin even with all that data if it is the wrong chipset? Would you give me the link to where I can check chipsets please?

[kcdtv]

maybe _ as suggested by data _ try without small "D.H." key ( no -S )
are you in hurry? because -d 0 is really fast and no delay 👯

Am I correct in thinking that pixiewps might not get the pin even with all that data if it is the wrong chipset?
absolutely. Every kind of chipset has it own breach and if no breach is known for you chipset then there is no miracle....

Would you give me the link to where I can check chipsets please? Weird question.... or i don't get it. Go to your manufacturer page to check that or you can check it out on a page like https://wikidevi.com/wiki/Main_Page have a look on your manual, they often have a data sheet where you should get this info. cheers

[thesolyom]

Thanks for the reply
In the last question I meant is there a database of chipsets that are susceptible to this kind of attack.. Thanks for the link, I'll have a read through that just in case.

In answer to my own question, list of chipsets and routers for pixiedust attack/or not

https://docs.google.com/spreadsheets/d/1tSlbqVQ59kGn8hgmwcPTHUECQ3o9YhXR91A_p7Nnj5Y/edit?pli=1#gid=2048815923

[soxrok2212]

Be sure to run reaver with -vvv and I recommend not using -S as it causes issues with realtek based routers.

[Despized]

had same issue to solve just leave the checksum (8th) digit off (only put in the first 7 digits) of the pin and run again in bully. I didnt check to see if this will work with reaver but it just might. Good luck

Despized

[kcdtv]

the PIN was given by reaver, it is 12345670 which starts any session if we don't use -p option
And it is working all time (by working i mean that you now if it is right or wrong)
in this case (old) what is weird is the PKR (00:00:00 etc. 00:02)
But the data are given and not all routers are vulnerable to pixiedust