ALLOW and SKIP buttons not working

[wokhan]

ALLOW and SKIP buttons not working

[Clyfton]

It doesn't matter what the port numbers and IP addresses are ... when I click ALLOW then I am saying that I trust the program and that I don't want to see any more notifications ever again from that program regardless of port or IP. That is standard firewall Ops. And yes, the ports and IPs are different. I don't know what you mean by the advanced panel expanded.

[Clyfton]

Yeah ... I kinda figured as I was typing my last rant that you guys were thinking CONNECTIONS and I was thinking PROGRAMS. You guys are way more nerdy than me (that's a compliment). I am not nerdy enough to think about the port and connection level. I just want to be able to trust programs so I don't get nagged by continuous prompts. Maybe you need an ALLOW CONNECTION and an ALLOW PROGRAM button. When you get the ALLOW PROGRAM button, I'll give it a try again :)

[AtlasHackert]

I assume you mean version 2 beta 1?

"Skip program" only skips current notifications; the skip-button (in V2 anyway) was never meant to permanently ignore connection attempt. In fact, if that's what you want, just create a block-rule: it's effectively the same: the connection gets blocked, and you don't get a notification.
Multiple prompts: are they really duplicates, or are they for different ports/IPs? Can you check the existing rules / check the options in the Advanced panel of the Notifier to see if they really are identical?

[Clyfton]

I do not want to block. As I mentioned above, I want to allow. That has been my problem with every version, repeated prompts for a program I have already allowed.

[AtlasHackert]

Can you check whether the rules are indeed identical, or if port numbers/IP addresses have changed? And post screenshots of the rules?
Can you please post a screenshot of the Notifier with the Advanced panel expanded of one of the connections that should have been allowed by the rules?

[AtlasHackert]

It doesn't matter what the port numbers and IP addresses are ... when I click ALLOW then I am saying that I trust the program and that I don't want to see any more notifications ever again from that program regardless of port or IP.

It depends on your viewpoint. Are you allowing the program, or the connection? I've got several programs where I allow certain ports, but not others... But it should be made more clear, I agree. I'll see what I can do about that.

You can customize the rules WFN creates by expanding that Advanced panel in the Notifier, and changing the options. The Advanced panel is the button at the bottom of the Notifier: https://camo.githubusercontent.com/b50db23cde74aef5bbc76661b0327be63bf2cc98/687474703a2f2f776f6b68616e2e6f6e6c696e652e66722f70726f67732f77666e2f6e6f7469666965722e504e47

[ahubbard]

Great work! I've been tracking your progress and donating periodically. I have the same issue and I'm using the advanced panel correctly. Screenshot attached
and it happens with most of my rules
I noticed the title bar says "WFN v2.0 ALPHA" but I confirmed I'm using the lastest beta with map db.

[AtlasHackert]

Maybe you need an ALLOW CONNECTION and an ALLOW PROGRAM button.

Yes, that is a good idea! I'll get working on that ASAP.

@ahubbard: The "Office Click to Run" files may not be identical; check the paths. Every different version installs in a different path, leading to many similar but not identical rules.
VNC Server: I'll check that out.
Title bar: And I'll fix that.

[AtlasHackert]

Figured out the problem of the VNC Server. It's one of these programs that's running a service, but starting connections outside of it. As a workaround: in the Advanced-panel, disable the checkbox for the "Service", and then create the rule.

[ahubbard]

Great for VNC. I've got several of these duplicates though :)

[AtlasHackert]

@ahubbard: I've released a new version, 2.0 Beta 2. Can you try that one for these programs? You should remove all those rules manually before, just to make sure they don't interfere.

@Clyfton: I haven't made separate buttons for connection vs program yet, but I've cleaned up the code around it, so it should now be easy to implement. Next release, hopefully!

[ahubbard]

Anectodately, I seem to be receiving less alerts overall. Looks like the new beta took care of VNC, no further alerts there. But the issue still remains for other services unfortunately:

and for non-services:

[wokhan]

Became a duplicate of #29 (sort of), for the "allow program" part. Closing this issue as it is already in our backlog.