This project has moved. For the latest updates, please go here.
1
Vote

Can't authorize torrent-client for all outbounds prompts

description

Tinywall permits a software exception which can be add as "service" "path .exe" or "ip". WFN blocking all outbounds not only hasn't that manual option but also calls a popup for every IP that connects to the torrent client that's more than 500 exceptions that renew every minute.

A "startup with windows" needs to be implemented as well. But the first issue makes no use of WFN software to me.

comments

DanielPharos wrote Apr 16 at 10:30 AM

Tinywall permits a software exception which can be add as "service" "path .exe" or "ip". WFN blocking all outbounds not only hasn't that manual option but also calls a popup for every IP that connects to the torrent client that's more than 500 exceptions that renew every minute.
You can customize the rule WFN is going to create by clicking the "Advanced" expander, and then toggling on/off the different options. In your case, you need to disable the "Target" and "Target port", and perhaps "Protocol" options before creating the rule.

p690026 wrote Apr 19 at 4:43 PM

Can't you make it easier by simplifying rules in the software itself? I see no purpose of using this software it if I have to configure everything manually at the windows control panel.

DanielPharos wrote Apr 19 at 5:09 PM

Sorry, I meant the "Advanced" expander in the Notifier window of WFN, not in the Windows Firewall control panel. (Although, of course, you can fix-up any existing rules there).

p690026 wrote Apr 21 at 2:17 PM

Where is it? "Advanced console" in firewall rules opens the windows control panel.
There are no "add path .exe" or "services".

DanielPharos wrote Apr 21 at 3:38 PM

Ah, I see where the confusion is coming from. The "Notifier" I'm talking about is the pop-up window. Right now, the console (WFN.exe) indeed has very limited functionality to change rules; it's on the ToDo list.