Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

It is fairly vague, so you'll have to show a screenshot (copy and paste text between the 'code' tags).

Hi,
While airodumb, I am not seeing the BSSID of the AP, which my secondary laptop is connected( got through netsh  wlan show intetfaces). Seems confused. What will be the reason?

Dear misterx,

I could not get a plausible response from my colleague in the industry.  Thank you for the help you have provided.

What change?

Dear misterx,

Thank you for your suggestions.  I would like to indicate that the issue I reported occurred on two different platforms.  I performed a memtest on both of these platforms and the test passed without any issues.  I used a memory block size of 10 GB with 10 iterations on one platform and a memory block size of 2 GB with 10 iterations on the other platform.

One of the colleagues with whom I work in the industry indicated to me that as per his investigation a change in the rtl8812au driver in the github directory was causing the corruption issue.  The path for the link is 'https://github.com/aircrack-ng/rtl8812au.git'.  To overcome the issue, he used the previously loaded rtl8812au driver from the same 'https://github.com/aircrack-ng/rtl8812au.git' link.

I used the procedure he provided.  Now, the Wi-Fi adapter associates with the router on both of the platforms.

Thank you for the help you have provided.  I appreciate it.

The wifi adapter's driver may not send ACK to userspace. In this case, there is also no client.

Get a client to connect and be active, and/or get another chipset.

Hi,

I don't see any ACKs after "Sending DeAuth (code 7) to broadcast — BSSID: [F8:AB:05:64:03:28]" when I try to attack my network.

I use

sudo airodump-ng -w hack1 -c 1 --bssid F8:AB:05:64:03:28 wlan0
and
sudo aireplay-ng --deauth 0 -a F8:AB:05:64:03:28 wlan0

wlan0     unassociated  ESSID:""  Nickname:"<WIFI@REALTEK>"
          Mode:Monitor  Frequency=2.457 GHz  Access Point: Not-Associated   
          Sensitivity:0/0 
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

see photo

What to do?

Yes. Just do the scanning next to the AP, and they will just show up on the screen.

Is there a way to scan for new devices that come into the range of our access points?

You'd have to see what changed exactly between these 2 kernel versions.

Another thing you can do is running a memtest overnight to check if you don't have any issue with the RAM (which could explain the corruption).