Apfree-wifidog Portable ❲Simple — 2024❳

Natively interfaces with telemetry engines through long-running WebSocket and MQTT connections.

Consider a stadium event: 5,000 users try to log in within 60 seconds. The original Wifidog would queue these requests, leading to timeouts. Apfree-wifidog, however, uses an event-driven model. While waiting for the remote Auth Server (e.g., a RADIUS or JSON API) to respond to Client A, it is already parsing the HTTP request from Client B and building the firewall rule for Client C. apfree-wifidog

Community networks (like Freifunk or Guifi) require strict authentication and logging. Apfree’s multi-threading allows a single gateway node to handle hundreds of mesh clients traversing the network. Apfree-wifidog, however, uses an event-driven model

To monitor real-time traffic and see who is authenticating: Apfree’s multi-threading allows a single gateway node to

ApFree WiFiDog operates using a decoupled, dual-component architecture:

This article is based on the state of apfree-wifidog as of 2024. For the latest source code and documentation, refer to the official GitHub repository.