Blog | G5 Cyber Security

Bully & Reaver Network Scan Issues

G5 Cyber Security

TL;DR

Bully and reaver aren’t finding networks? This guide covers common problems and fixes, from wireless adapter issues to incorrect settings. We’ll focus on ensuring your hardware is compatible, drivers are up-to-date, and you’re running the tools correctly.

Troubleshooting Steps

  1. Check Wireless Adapter Compatibility
    • Bully and reaver require a wireless adapter that supports monitor mode and packet injection. Not all adapters do!
    • Common compatible chipsets include Atheros, Ralink, and Realtek (but check specific models).
    • Use Wireless Adapter Compatibility to verify your adapter’s capabilities.
  2. Update Wireless Adapter Drivers
    • Outdated or incorrect drivers are a frequent cause of problems.
    • Download the latest drivers from the manufacturer’s website (Atheros, Ralink, Realtek, etc.). Do not rely on Windows Update alone.
    • After installing, restart your computer.
  3. Verify Monitor Mode is Enabled
    • Bully and reaver need to put your wireless adapter into monitor mode to capture network traffic.
    • Use Aircrack-ng documentation for instructions specific to your operating system (Linux is generally easier).
    • On Linux, you might use commands like:
    sudo airmon-ng start wlan0

    (Replace wlan0 with your wireless interface name. Use iwconfig to find it.)

  4. Check for Interference
    • Other wireless devices, microwaves, and physical obstructions can interfere with network scanning.
    • Try moving closer to the target access point or changing your location.
    • Temporarily disable other nearby wireless devices.
  5. Run Bully Correctly
    • Ensure you’re using the correct interface name with Bully.
    • Example command:
    sudo bully wlan0mon

    (Again, replace wlan0mon if your monitor mode interface has a different name.)

  6. Run Reaver Correctly
    • Reaver requires the BSSID (MAC address) of the target access point. You can find this using Bully or other network scanning tools like Airodump-ng.
    • Example command:
    sudo reaver -i wlan0mon -b [BSSID] -vv

    (Replace wlan0mon with your monitor mode interface and [BSSID] with the target access point’s MAC address.)

  7. Check Channel Hopping (Reaver)
    • Reaver needs to hop between channels to find the target network. Ensure it’s not being blocked by channel restrictions.
    • If you know the target access point’s channel, specify it with the -c option:
    sudo reaver -i wlan0mon -b [BSSID] -c [channel] -vv
  8. Firewall and Security Software
    • Some firewalls or security software may block Bully or Reaver. Temporarily disable them to see if that resolves the issue (be careful when doing this!).
  9. Check for Virtual Machines/Docker
    • Running Bully and reaver inside a virtual machine or Docker container can sometimes cause issues with wireless adapter access. Try running them directly on the host operating system.

Further Help

If you’ve tried these steps and are still having problems, consult the official documentation for Bully (Bully GitHub) and Reaver (Reaver GitHub). The cyber security community forums are also a good resource.

Exit mobile version