Loqin keeps captive-portal Wi‑Fi sessions alive with zero-click re-login
Keep a campus or shared network connected by running Loqin PC as a system-tray client that detects session drops and performs automatic re-authentication. Created by Aayush Srivastava for VIT hostel Wi‑Fi, the utility uses OS-native credential storage and live monitoring to avoid repeated manual logins. It targets students and residents who face captive-portal timeouts and prefers a lightweight background tool that runs without a visible window once initial setup completes.
What the tool actually does in captive-portal networks
Loqin monitors the local network interface and triggers the portal sign-in sequence when the connection returns to an unauthenticated state. Built in Python, the client sits in the Windows system tray and performs the sequence automatically after you supply credentials once. Its workflow replaces the manual step of opening a browser to accept a captive portal, so the machine regains authenticated access without user intervention.
How it affects system resources during continuous operation
Because the app uses a lightweight Python-based architecture and runs from the system tray, it imposes a modest footprint on a typical desktop. The design emphasises low background usage by polling the connection state rather than running heavy scans, which keeps CPU and memory demands small on an idle student laptop. Processes stay out of the foreground, reducing interference with other applications.
Whether it stores credentials and how it protects them
Loqin stores login details using the operating system's native credential facilities, so passwords remain on the local machine instead of plain text files. The app's open-source GPLv3 license lets technically proficient users inspect the code paths that access those APIs. This architecture matches common expectations for a tool that must submit credentials to a captive portal automatically.
Who can operate it and what technical skill is needed
Initial setup requires entering portal credentials and granting the client access to native credential storage, a task suitable for users comfortable with a short configuration step. In addition, users who want to review or contribute can read the source code because the project is open under GPLv3. Less technical users can run the app after setup without interacting with login pages again.
Reliable niche utility for recurring captive-portal logins, with one clear trade-off
Loqin performs the core job of keeping sessions authenticated for users on captive-portal networks, using OS-backed credential storage and a low-overhead background process. It suits students and residents who need persistent connectivity without repeated browser logins. The main trade-off is that it automates credentials on the local machine, so its value depends on whether you accept local storage of your portal login for convenience.
