Skip to content
MangoWiFi

  • MangoFly

    A self-hosted WireGuard mesh. Devices connect straight to each other; the coordination server is one binary and a SQLite file, and never sees their traffic.

    ExploreDocsPricing
    encrypted WireGuard · peer to peerLaptopbehind home NATServerin a datacentrePhoneon mobile datacoordination serverone binary · one SQLite filecontrol plane only (TLS)keys · tunnel addresses · peer lists · sealed ICE candidatesholds no private keys · carries no traffic · cannot decryptdatacontrol

  • MangoDock

    Docker management with nothing on the hosts. Reaches each daemon over an ordinary SSH session — no agent to install, no port to open.

    ExploreDocsPricing
    The MangoDock dashboard showing three host cards with container state counts, CPU and memory gauges, a usage history and recent events

  • MangoWiFi

    A Wi-Fi 6/7/8 test bench. One binary runs as Console or Agent either side of the access point under test, measuring latency under real load.

    ExploreDocsPricing
    AP under testWi-Fi 6 / 6E / 7Agentstation side · real radioLAN receiveriperf3 -sConsoleUI · orchestrates · probes
  • Blog

  • Nothing phones home

    No telemetry, no analytics, no crash reporter, no account login. Check it with a packet capture on your own network.

    Download MangoSSH
  • Project
  • Download

    • Baseline checks

    The twenty-four pre-flight checks, and why they run first.

    Baseline: 24 pre-flight checks across six categories, each marked required or advisory. Run before anything that produces a number.

    Baseline answers a different question from the rest of the catalog: not how well the AP performs, but whether this bench can measure anything at all. Running it first turns a confusing performance result into an obvious missing dependency.

    Environment

    • Kernel version — new enough for the driver.
    • Regulatory domain — which channels and powers are legal here.

    Radio

    • Primary radio present, and which driver is bound to it.
    • Reported capabilities and antenna mask.
    • Monitor radio present, if passive capture is wanted.

    Station

    • iw version, and wpa_supplicant on PATH.
    • Virtual interface creation — the basis of multi-client simulation.
    • MAC programmable, so simulated stations are distinguishable.

    RF and AP

    • Scan returns results; noise floor and channel utilisation are sane.
    • Attenuator responds, where one is fitted.
    • The target SSID is visible, associates, gets a DHCP lease, and reports an RSSI baseline.
    • The LAN side answers a ping.

    Traffic

    • iperf3 and capture tools present on the Agent.
    • The LAN receiver is reachable and its iperf3 is listening.
    ← Installation & first runWi-Fi 8 (802.11bn D2.0) →