Sinisterly
Cannot capture handshake when sniffing - Printable Version

+- Sinisterly (https://sinister.ly)
+-- Forum: Hacking (https://sinister.ly/Forum-Hacking)
+--- Forum: Network Hacking (https://sinister.ly/Forum-Network-Hacking)
+--- Thread: Cannot capture handshake when sniffing (/Thread-Cannot-capture-handshake-when-sniffing)

Pages: 1 2

RE: Cannot capture handshake when sniffing - L0aD1nG - 09-24-2014

And I am back not with suggestions though, but with some useful annotations.

So I am out of internet connection, although I found out 3 passwords they are all VERY VERY VERY slow...and I am trying rarely now (from the day I found the 3 I mentioned) to find some new passwords with better signal.

As I was in the process yesterday I realized that a weird thing was happening when I was running:
Code:
airodump-ng --ignore-negative-one mon0
It seemed that all the routers that were listening on channel 1 had more focus on scanning than all the others causing me not to get all the possible routers on my terminal scan. I tried some weird things (coming through my head) but nothing seems to be working... Then I remembered what you mentioned about the permanent fix of:
Quote:mon0 on fixed channel -1

You said on some previous post that you are doing this:
Code:
ifconfig <real wireless interface> down
To prevent permanently that problem. And I said that this was wrong and in fact IT IS, but your way has its advantages at least it shows to.

Let me explain what happended next.
So after thinking about what you said I told to myself lets give it a try properly so I start doing everything from the start and when I was on the mac changing process I let the interface down for ever. Then I started the:
Code:
airodump-ng mon0
And everything seemed to work fine... I thought "Oh that guy had right on this, it works!". Continueing on the process of getting a Handshake of a WPA2 router and everything seemed to work properly. After sometime of scaning specific routers (2 on same time), on the one of them a client appears! So I go straight forward to deauth him fast so I don't loose the chace of getting the handshake. The router was to hard to get the handshake with 1 package, everything was still fine, so I go low spamming it with 10 packages.THEN something really weird happend!

My scan terminal totally stucked up anything was working even the beacons was stucked up but the router and the client was still up and running! I said that weird maybe my laptop is jerking off I will retry, I went retring the same process on the same router this time I had more time deauthing but still the same thing happended. Then I went to another router with not that good signal but with a client on it... same thing happens again!

So my conclusion is at least in my opinion from the experience I have on aircrack is that your reccomendation about:
Code:
ifconfig <interface> down;
and letting it like this, works nice on scanning and its better to use it like this when we are scanning for wifi networks. But when we find our target its impossible to transmit packages to him that way we MUST bring the interface up before we start the specific router scan so we are able to prevent on any attacks we want and use any kind of packages transfer we want without stucking up and loosing what we have done so far... I know that --ignore-negative-one in some cases doesn't fix the problem but its rare, the only problem that is really unfixed by that parameter atm is when you scan on every channel cause it is forced for some reason to pay more attention on routers that are listening on channel 1.

Thats my updates annotation for the new buggy beta aircrack version. Just to give more info to any HC member read that post and our discussion. Some of the next day I will try the same thing with the interface down on a WEP thing that I didn't on my journey th day before yesterday!

At last I had no time to recheck this post about crappy english usage, I hope my english didn't tired you much to read this dude... if anything has been written that doesn't make sense please let me know... and I will explain it better(at least I will try to next time I will be available to access the internet).
Keep it up!
Cheers!

RE: Cannot capture handshake when sniffing - L0aD1nG - 09-24-2014

And I am back not with suggestions though, but with some useful annotations.

So I am out of internet connection, although I found out 3 passwords they are all VERY VERY VERY slow...and I am trying rarely now (from the day I found the 3 I mentioned) to find some new passwords with better signal.

As I was in the process yesterday I realized that a weird thing was happening when I was running:
Code:
airodump-ng --ignore-negative-one mon0
It seemed that all the routers that were listening on channel 1 had more focus on scanning than all the others causing me not to get all the possible routers on my terminal scan. I tried some weird things (coming through my head) but nothing seems to be working... Then I remembered what you mentioned about the permanent fix of:
Quote:mon0 on fixed channel -1

You said on some previous post that you are doing this:
Code:
ifconfig <real wireless interface> down
To prevent permanently that problem. And I said that this was wrong and in fact IT IS, but your way has its advantages at least it shows to.

Let me explain what happended next.
So after thinking about what you said I told to myself lets give it a try properly so I start doing everything from the start and when I was on the mac changing process I let the interface down for ever. Then I started the:
Code:
airodump-ng mon0
And everything seemed to work fine... I thought "Oh that guy had right on this, it works!". Continueing on the process of getting a Handshake of a WPA2 router and everything seemed to work properly. After sometime of scaning specific routers (2 on same time), on the one of them a client appears! So I go straight forward to deauth him fast so I don't loose the chace of getting the handshake. The router was to hard to get the handshake with 1 package, everything was still fine, so I go low spamming it with 10 packages.THEN something really weird happend!

My scan terminal totally stucked up anything was working even the beacons was stucked up but the router and the client was still up and running! I said that weird maybe my laptop is jerking off I will retry, I went retring the same process on the same router this time I had more time deauthing but still the same thing happended. Then I went to another router with not that good signal but with a client on it... same thing happens again!

So my conclusion is at least in my opinion from the experience I have on aircrack is that your reccomendation about:
Code:
ifconfig <interface> down;
and letting it like this, works nice on scanning and its better to use it like this when we are scanning for wifi networks. But when we find our target its impossible to transmit packages to him that way we MUST bring the interface up before we start the specific router scan so we are able to prevent on any attacks we want and use any kind of packages transfer we want without stucking up and loosing what we have done so far... I know that --ignore-negative-one in some cases doesn't fix the problem but its rare, the only problem that is really unfixed by that parameter atm is when you scan on every channel cause it is forced for some reason to pay more attention on routers that are listening on channel 1.

Thats my updates annotation for the new buggy beta aircrack version. Just to give more info to any HC member read that post and our discussion. Some of the next day I will try the same thing with the interface down on a WEP thing that I didn't on my journey th day before yesterday!

At last I had no time to recheck this post about crappy english usage, I hope my english didn't tired you much to read this dude... if anything has been written that doesn't make sense please let me know... and I will explain it better(at least I will try to next time I will be available to access the internet).
Keep it up!
Cheers!

RE: Cannot capture handshake when sniffing - Master Antrax - 09-25-2014

If you used a tutorial you should make sure everything you did is correct and if that does not work I am sure someone on here knows.

RE: Cannot capture handshake when sniffing - Master Antrax - 09-25-2014

If you used a tutorial you should make sure everything you did is correct and if that does not work I am sure someone on here knows.