search

henrypp / simplewall

Simple tool to configure Windows Filtering Platform (WFP) which can configure network activity on your computer.
GNU General Public License v3.0
6.29k stars 487 forks source link

Notifications open too late or never #256

Closed LtqxWYEG closed 5 years ago

LtqxWYEG commented 6 years ago

Hi

I found that Notifications appear very late, all the time. (10-30s delay) Also, if two applications are blocked at the same time and both produce (or should) notifications, only one notification is shown.

best regards

Tom4tot commented 6 years ago

I have the same issue, it seems to concern all apps. I'm running Windows 10 1809.

LtqxWYEG commented 6 years ago

Oh sorry: Windows 10 pro 1803 Sometimes they don't even bother to show up at all until I manually add the program.

ltguillaume commented 5 years ago

Same here. Shouldn't simplewall validate the "event hook" it's got every minute or so? I guess it's losing that somehow.

Tom4tot commented 5 years ago

Hi, thank you for your last update and for your hard work.

However, even after a clean install (portable version), I still have delays with notifications. I'd say it's most of the time 5-15 seconds. For me they always eventually arrive, just with a little delay. It's not a huge issue honestly but I just wanted to give you some feedback.

henrypp commented 5 years ago

@Tom4tot, delays for notifications (5-15 seconds) is normal thing, because simplewall used only one thread to parse all dropped packets queries pool, and delay depends on simplewall settings (network address resolver, check apps signature and some another more).

LtqxWYEG commented 5 years ago

This still happens for me sometimes. I even unchecked resolving addresses and signatures.

henrypp commented 5 years ago

@Distelzombie how late is it?

LtqxWYEG commented 5 years ago

Sometimes it never appears. Just now with whois64.exe from sysinternals the notification never appeared. Only AFTER I added and allowed it myself a notification popped up asking about access to 127.0.0.1 - but it was already allowed.

Again, I have "resolve domain names" and "check signatures" already disabled.

EDIT: I removed it from the list in Simplewall and tried again: No notification appears. Even after several restarts of whois64. This is on 2.3.10

EDIT: I just had one appear 10 seconds after my last attempt finished and the process has already been eliminated.

paradoxicallist commented 5 years ago

Still happening on 2.3.11

Now, in order to bring up a notification I close main gui and relaunch again but a new error shows in the logfile: ‎23-‎Dec-‎18 ‏‎10:27:03 AM,FwpmEngineSetOption(),0x00000005,FWPM_ENGINE_COLLECT_NET_EVENTS,2.3.11 ‎23-‎Dec-‎18 ‏‎10:27:07 AM,FwpmEngineSetOption(),0x00000005,FWPM_ENGINE_COLLECT_NET_EVENTS,2.3.11 ‎23-‎Dec-‎18 ‏‎10:27:07 AM,FwpmTransactionCommit(),0x00000005,#2123,2.3.11 ‎23-‎Dec-‎18 ‏‎10:27:07 AM,FwpmTransactionCommit(),0x00000005,#4319,2.3.11 ‎23-‎Dec-‎18 ‏‎10:27:22 AM,FwpmEngineSetOption(),0x00000005,FWPM_ENGINE_COLLECT_NET_EVENTS,2.3.11 ‎23-‎Dec-‎18 ‏‎10:27:22 AM,FwpmTransactionCommit(),0x00000005,#2123,2.3.11 ‎23-‎Dec-‎18 ‏‎10:27:22 AM,FwpmTransactionCommit(),0x00000005,#4319,2.3.11 ‎23-‎Dec-‎18 ‏‎10:38:01 AM,FwpmEngineSetOption(),0x00000005,FWPM_ENGINE_COLLECT_NET_EVENTS,2.3.11 ‎23-‎Dec-‎18 ‏‎10:38:01 AM,FwpmTransactionCommit(),0x00000005,#2123,2.3.11 ‎23-‎Dec-‎18 ‏‎10:38:01 AM,FwpmTransactionCommit(),0x00000005,#4319,2.3.11

Polisson commented 5 years ago

Still on beta 2.4, Win 8.1 In my case I can't to force showing up notifications at all.

logfile: "‎2019-‎02-‎27 ‏‎12:28:44","FwpmEngineSetOption()","0x00000005","FWPM_ENGINE_COLLECT_NET_EVENTS","2.4"

henrypp commented 5 years ago

On latest beta (2.4.2) notifications processing speed is improved.