iWifi

Rating: 
5
Your rating: None Average: 5 (1 vote)

iWifi turns a Sailfish OS phone into a passive Wi-Fi security checker: a heading-up radar of the access points around you, a per-hotspot security assessment, CVE lookup for the router model, and an optional monitor mode (external USB adapter) that defensively detects deauthentication attacks and evil-twin APs. It never transmits, injects, cracks or decrypts anything.

FEATURES
- Radar (entry screen): heading-up view of nearby APs, filter by channel/RSSI, 2.4/5 GHz band filter, pin hotspots; optional GPS fix and opt-in OpenStreetMap silhouette (that query sends the bounding box of your position to a public Overpass mirror - only when you switch it on)
- Network list and detail view per hotspot: vendor (BSSID OUI), band/channel, signal and rough distance, security class (open / WEP / WPA2 / WPA3 / WPA3-transition / Enterprise), cipher, PMF/802.11w, advertised client count, country, hidden-SSID and randomized-MAC flags, WPS info
- CVE lookup for the router model (NIST NVD) with CISA known-exploited flag and Exploit-DB link - network access only when you tap it
- Monitor mode (optional, needs an external adapter and a monitor-mode driver, see the README): deauth/disassoc attack detection, evil-twin detection, connected-client count per AP shown as anonymous dots - no client identities are shown or stored
- LAN device list (ARP) for your own connected network
- Stores nothing: no export; the monitor snapshot is a volatile file in RAM, deleted when monitoring stops

PLEASE READ - WHAT THE PACKAGE INSTALLS SYSTEM-WIDE
For the optional monitor mode the package ships a root systemd unit (harbour-iwifi-monitor.service: brings wlan1 up in monitor mode and runs the sniffer; not enabled at boot, started only by the app while it is in the foreground), a polkit rule that lets the phone's user start/stop exactly that one unit, a system D-Bus policy for reading wpa_supplicant scan results, and a Sailjail permission that gives the sandboxed app host network and a shared /tmp. No kernel driver is included - monitor mode needs an external adapter and a driver you build yourself (see the README). rpm -e removes all of it. The LAN device list asks your own router (TR-064) for its host list.

STATUS 
Developed and tested on J2 and Xperia10III and the monitor-mode driver is built for that kernel. Monitor mode receives 802.11 management frames: use it on your own network or where you have permission. Use it to understand and harden your own Wi-Fi.

ARCHITECTURES
aarch64 (Sailfish OS 5.0). No armv7hl build.

Written with Claude Code (Anthropic).

Source, issues, releases: https://github.com/JimKnopfIoT/harbour-iwifi, GPLv3

 

Application versions: 
AttachmentSizeDate
File harbour-iwifi-1.0.1-1.aarch64.rpm687.22 KB30/08/2026 - 21:00
Changelog: 

(none)

Comments

aviarus's picture

Sounds very cool. Monitor mode driver must have been hard work

JimKnopfIoT's picture

You need external hardware for that. Alfa Network Card for example. But, the advantage is, you can detect a deauther.