-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tinywall is blocking System Executable even though it has no restrictions #6
Comments
Probably because ICMP traffic is still being filtered. You can deactivate this filtering in the Recommended list on the Special Exceptions tab. You'll be giving up a little bit of extra security. |
I tried it both to check and uncheck Filtered ICMP Traffic in the Special Exceptions tab. I occasionally see the System Executable is blocked for ICMPv4 when I click show connections. I tried this on multiple PCs. |
Also when I connect to a VPN, I see the System Executable is blocked for ICMPv6, IGMP, and UDP port 137 for source and destination. Filtered ICMP Traffic in the Special Exceptions tab is unchecked and the System Executable is allowed with no restrictions. I am using the latest version of tinywall as of now 3.3.1. |
Then something else must be blocking those packets, for example standard firewall rules in Windows. Note that TinyWall lists blocked packets and connections even when they weren't blocked by TinyWall itself. Anything that gets blocked (for whatever reason or through whichever software) inside the Windows Filtering Platform component of Windows ends up in TinyWall's blocked list. |
I have same issue. Occurred as soon as I shutdown pc forcefully. Currently there's 2 issues:
I'm using 3.2.5 |
Reinstalling solves it. |
I had a VPN that, no matter what else I tried, I couldn't get to connect until I checked the "unblock LAN traffic" option. I did it a long time ago but never got to circle back around to really investigating it. |
Same issue, "System" to icmpv4 to gateway is blocked ("No Restrictions" and 'Apply to Children') . Another other program that is blocked too with various remote address ports. EDIT: I should also note, if I also change Tinywall to "ALLOW OUTGOING" it still blocks them. |
Also having this issue. Can confirm like @graysuit said that reinstalling fixes it. However over the last few months I've already had to reinstall twice and looking at a 3rd time. This is not a viable long term solution. As others described I can have a program managed to give full access + child processes and it doesn't matter. Additionally trying to allow a program access by right right-clicking in the "blocked connections" and selecting unblock also doesn't work. |
First of all an amazing piece of software.
The issue is when I check the blocked connections, it is blocking the System Executable for ICMPv4 protocol to IP 8.8.4.4 even though the System Executable is allowed with no restrictions.
The text was updated successfully, but these errors were encountered: