Skip to content
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

Open
michaelsoliman-com opened this issue Apr 9, 2023 · 11 comments

Comments

@michaelsoliman-com
Copy link

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.

@michaelsoliman-com michaelsoliman-com changed the title Tinywall is blocking system process even though it has no restrictions Tinywall is blocking System Executable even though it has no restrictions Apr 9, 2023
@pylorak
Copy link
Owner

pylorak commented Apr 13, 2023

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.

@michaelsoliman-com
Copy link
Author

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.

@michaelsoliman-com
Copy link
Author

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.

@pylorak
Copy link
Owner

pylorak commented Apr 17, 2023

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.

@michaelsoliman-com
Copy link
Author

I have windows firewall disabled on my 2 machines. Here is a screenshot of what is showing
image

@graysuit
Copy link

I have same issue. Occurred as soon as I shutdown pc forcefully.
maybe its corrupted or updated ?

Currently there's 2 issues:

  • It blocks traffic even excluded (have to modify, make it NO RESTRICTIONS + APPLY TO CHILD PROCESSES)
  • It doesn't remember excluded items on next restart. Have to again exclude programs.

I'm using 3.2.5
Also please don't force net 4.8. I do have windows 10, but 2015 version where 4.8 doesn't installs.
So I thinks its too early to make it windows 10 or 11 only app

@graysuit
Copy link

I have same issue. Occurred as soon as I shutdown pc forcefully. maybe its corrupted or updated ?

Currently there's 2 issues:

* It blocks traffic even excluded (have to modify, make it NO RESTRICTIONS + APPLY TO CHILD PROCESSES)

* It doesn't remember excluded items on next restart. Have to again exclude programs.

I'm using 3.2.5 Also please don't force net 4.8. I do have windows 10, but 2015 version where 4.8 doesn't installs. So I thinks its too early to make it windows 10 or 11 only app

Reinstalling solves it.

@spacewaffles309
Copy link

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.

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.

@michaelsoliman-com
Copy link
Author

michaelsoliman-com commented May 21, 2023

Also this is an issue with VMware Workstation Pro. I have [no restrictions + apply to child processes] set for VMware NAT Service (C:\Windows\SysWOW64\vmnat.exe), and it's still blocked by the firewall

image

@QGtKMlLz
Copy link

QGtKMlLz commented Jun 9, 2023

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.

@Shuggaloaf
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants