search

intrig-unicamp / mininet-wifi

Emulator for Software-Defined Wireless Networks
https://mn-wifi.readthedocs.io/
Other
438 stars 239 forks source link

How to find all clients and BSSIDs with airodump-ng ? Need to get handshakes #294

Closed kogonidze closed 2 years ago

kogonidze commented 4 years ago

I tried two ways to solve this problem. 1) Create a new monitor interface with sta1.cmd('iw dev sta1-wlan0 interface add mon0 type monitor') then airodump-ng mon0 Result: find only BSSID of ap1 (sta1 connected with ap1) and connection between sta1 and ap1. You can see that on the first screenshot. So, I can get a handshake only for first network.

2020-04-01_19-57-36

2) Change the existing interface sta1-wlan0 with airmon-ng check kill airmon-ng start sta1-wlan0 airodump-ng sta1-wlan0mon Result: find all BSSID but no one client. So, I can't get any handshake at all. You can see that on the second screenshot. 2020-04-01_20-07-59

So, is it possible to find all BSSID and clients with airodump-ng? And get 7 handshakes.

ramonfontes commented 4 years ago

Sorry, is this issue related to Mininet-WiFi or airodump-ng?

kogonidze commented 4 years ago

Sorry, is this issue related to Mininet-WiFi or airodump-ng?

Of course to Mininet-WiFi. I was interesting to try hacking virtual Wi-Fi networks on Mininet-WiFi and I ran into this problem.

ramonfontes commented 4 years ago

Didn't you kill the _wpasupplicant process of the other stations with airmon-ng check kill?

kogonidze commented 4 years ago

Didn't you kill the _wpasupplicant process of the other stations with airmon-ng check kill?

Yes, you are right. I really killed the wpa_supplicant processes of all other stations.

But without airmon-ng check kill I get this error: 2020-04-01_21-05-22 2020-04-01_21-06-08

ramonfontes commented 4 years ago

You may want to stop only the network-manager process instead of using airmon-ng check kill. However, I'm curious why 1 didn't work. It seems that airodump-ng was filtering beacons on channel 1.

kogonidze commented 4 years ago

You may want to stop only the network-manager process instead of using airmon-ng check kill.

Yes, I stopped the network-manager and other services without airmon-ng check kill. And then run successfully command airmon-ng start sta1-wlan0. But got the previous result by the command airodump-ng sta1-wlan0mon: found all BSSIDs without any clients.

It seems that airodump-ng was filtering beacons on channel 1.

Unfortunately no. I ran airodump-ng without any filter (you can even see on the first screenshot that airodump-ng checked the channel 13 on that moment of the time).

ramonfontes commented 4 years ago

Strange. I'll give it a try as soon as possible. You can also try containernet (https://github.com/ramonfontes/containernet). Since each node has its own container you won't have problem if you run airmon-ng check kill.

ramonfontes commented 2 years ago

Closing due to inactivity