ATK Network Connection

Connect the ATK module to a Wi‑Fi network for client-side attacks.

ATK Network Connection

Many attacks (DHCP Starvation, packet capture, captive portal passthrough, etc.) require the ATK co-processor to join a target network in station mode. Use the Settings → Connect → ATK Network Connection panel in the Web UI to supply credentials and (optionally) randomize the ATK MAC address.

Connecting the ATK bridge

  1. Navigate to Settings → Connect and select the ATK Network Connection tab.
  2. Enter the target SSID and (if required) the WPA/WPA2/WPA3 password.
  3. Toggle Random MAC if you want the ATK to use a locally-administered address for the next connection.
  4. Click Connect. The status badge changes to Connecting… then updates to Connected to <SSID> (<IP>) once the ATK reports success.
  5. Use Disconnect to tear down the link and clear any temporary DNS passthrough settings.

Tip: The badge and SSID preview are shared with other cards (e.g., DHCP Starvation). If another page says “ATK network not connected” come back here, connect, and then return to the attack page.

Random MAC behaviour

  • The toggle simply instructs the device to enable or disable MAC randomization for the next connection attempt.
  • When enabled, the ATK STA manager picks a locally-administered (02:xx:xx…) MAC before every connection attempt. Disable the toggle to restore the factory MAC.

Troubleshooting

  • Stuck on “Queued” or “Busy”: another ATK operation is running. Stop it, then retry the connection.
  • No IP / captive login loop: check the target network’s security type and channel. Re-enter credentials or disable random MAC if the AP filters unknown OUIs.
Previous
File Manager