PacketHound Uses Windows Firewall for Little Snitch-Style Outbound Prompts
PacketHound sets Windows Firewall to block outbound connections by default and watches event 5157 to ask about third-party apps. Rules are ordinary Windows Firewall rules, with no kernel driver.
Outbound blocking
PacketHound is free software under the GPLv3 license. It builds on Windows Firewall rather than adding a kernel driver. It changes the default outbound action to Block on the Domain, Private, and Public profiles. Failure auditing for the Filtering Platform Connection is enabled, so every blocked attempt is written to the Security log as event 5157. PacketHound subscribes to those events. When a program without a rule tries to connect, the tool first decides whether the program counts as a Windows component. Windows components receive an allow rule silently; third-party apps bring up a prompt showing the app, publisher, destination hostname or IP, port, and protocol. Choosing Allow or Block creates an outbound rule in the PacketHound group. Windows itself is never prompted.
Rules and user control
A new rule can cover any connection for the whole app, only the current IP address, or a specific host and its subdomains. Since Windows Firewall matches only IP addresses, PacketHound updates the address list for host and domain rules as the app connects to new addresses; the app may need to retry once. Rules can last forever or until the app quits. Choosing Decide later keeps the connection blocked and places the app under “Waiting for your decision” on the Rules tab. Programs running from temp folders are treated as installers or updaters. If such a program is validly signed and allowed, future copies with the same file name and signer are allowed without a prompt. PacketHound watches temp folders, checks the signature before the program runs, and holds the file open to prevent replacement. If it is too late, a notification offers to pause protection for five minutes. The installer is self-contained at about 65 MB and installs to C:\Program Files\PacketHound. A scheduled task starts PacketHound elevated at sign-in, so there is no UAC prompt each time. The main window has Rules, Activity, and Settings tabs. Rules can be searched and sorted; a status column shows temporary rules, disabled rules, and programs that are no longer installed. Activity lists blocked attempts and lets users copy IP addresses. Settings includes a weekly update check that contacts packethound.app/version.php. PacketHound does not download or install updates. Its own outbound rule allows only HTTPS TCP 443; switching that rule to Block stops update checks. Prompts appear on top without taking keyboard focus, so typing never answers by accident.
Pause, exit, and limitations
Protection can be paused for 5 minutes, 15 minutes, one hour, or until manually resumed. Timed pauses restore automatically, including after a restart. While paused, apps without a rule can connect, but existing block rules still apply. On exit, PacketHound asks whether to keep blocking apps without a rule while it is closed; answering no pauses protection. Uninstall restores the original outbound default and audit setting after optionally deleting PacketHound’s rules.
The first connection from an app fails because PacketHound learns about the app from a blocked event. After Allow, the app has to retry; many browsers only need a refresh. Holding a connection open for a decision would require a signed kernel-mode WFP callout driver, which PacketHound does not use. Host and domain rules resolve to IP addresses, so sites behind the same CDN address share a rule. On managed PCs, Group Policy overrides local firewall changes. Auditing also logs blocked inbound connections, so the Security log fills faster than usual.