Weird, I could swear you mentioned somewhere that you was planning to develop a new GUI. But no big deal, the old GUI works just fine but a new GUI is always exciting to me. And what exactly means migrating away from .NET 3.5, I assume you will switch to another coding language?
Language will stay the same (C#), only the requirements will be upped to the latest version of the .Net Framework. Strictly speaking, this in itself is not a big undertaking. What makes this task bigger is to make use of the new possibilities this gives me in connection with dropping Win7 support. Otherwise there'd be no point upgrading if I don't utilize the advantages.
OK I see, so you will be moving to a newer .NET version, I'm guessing that us users will also have to upgrade then. I was never a big fan of this .NET stuff. I'm also still using Java because I'm using JStock, luckily I don't have to update it that often. https://jstock.org/index.html
You won't need to update your .Net Framework as long as you're running a supported Windows version, because the correct version will be included by standard. But all this doesn't apply yet to the current release in making.
Hi, around the time of the latest update I started getting gigabytes of data logged in Security.evtx - events 5152, 5156, 5158 multiple times per second: The Windows Filtering Platform blocked a packet Windows Filtering Platform has permitted a connection The Windows Filtering Platform has permitted a bind to a local port I can disable the logging itself via some auditpol console commands, but could this be related to the latest tinywall update? I can't think of anything else i've updated lately. Windows 7 64bit.
Do you use TinyWall in Autolearn a lot? Otherwise these aren't coming due to TinyWall. Also, according to my changelogs, there hasn't been a related change in the past three releases.
No autolearn. I tried disabling (and closing) tinywall and the events keep coming, so it's probably something else, sorry. No idea what, though.
TinyWall uses these auditlogs during autolearn. But it only enables these logs when you actually enter autolearn and then disables them immediately when you exit autolearn, so they don't stay enabled longer than absolutely necessary. In other words, your problem is probably due to something else. Some other firewalls though used to need these logs for their regular operation (don't know of they still do). Maybe it was another product that you tried earlier?
Oh wait, I thought the 3.0.10 was a recent update. Now I see from the changelog it's actually from 04.11.2020. My tinywall spontaneously switched languages (to my system language) a few days ago. I thought it was an update sideffect. If there was no recent update, maybe other settings somehow got messed up on my end too - including the logs. I watch my SSD writes every few days and I've been using tinywall exclusively for the past 5 months, so unless a Zoom or Firefox update triggered the log settings change, tinywall still seems like the most likely culprit. EDIT: So after succesfully disabling the logging yesterday (via console commands), I tried switching to "Autolearn" and back to "Normal protection" a few minutes ago and, unfortunately, the logging is back even when i'm on Normal protection. Weird! Switched it off via the console again.
Then you might have found a bug if it doesn't get disabled when going back to Normal mode. I'll check this in the evening.
Yep, you found a bug, thanks for reporting! Fixed in the upcoming release. It didn't get correctly disabled when autolearn terminated. So it was on if you ever started autolearn even for just a short time.
I just discovered that my Port 1025 is OPEN. Why is Tinywall not blocking it? This is not good of course.
Which process is keeping it open? That and send me an export of your TinyWall settings to inspect it.
Hello Everyone! Version 3.1 is almost done, or basically done unless something unexpected crept in. Hence I'm linking the release candidate here, I'd be thankful if a few of you could check it and give feedback whether it works alright. - Changelog is here. All known issues fixed and some new features incorporated. I will provide some additional release notes when the final release is made. - Version numbering has slightly changed. This has no significant meaning, but it allows me to version RC/test/beta releases correctly. Hence from now on there is no need to explicitly uninstall an older version when installing a test release. - As usual, test releases are not signed. Link to Release Candidate
OK cool, I sometimes get to see that certain apps won't work because I'm still using an older .Net version. That's why I have never been a fan of it. BTW, what exactly does the ''unblock LAN traffic'' setting do? I must say that after enabling this setting I almost never have any connection problems with my Devolo powerline adapters anymore. But not sure if it's related to this.
Allow me to quote the FAQ to answer your question: What is the "Unblock LAN traffic" option for? It is an option to easily allow network traffic from/to the local network. It is most useful if you only wish to limit internet traffic. Normally, when TinyWall is operating in "Normal" mode with this option unchecked, it will block all traffic except for whitelisted applications. But if "Unblock LAN traffic" is checked, traffic from/to the LAN will be allowed by default even in "Normal" mode. Basically, if this option is enabled, TinyWall behaves as if the firewall was mostly disabled for the local network, but enabled for the internet.
TinyWall 3.1 released! All known issues to date have been fixed and of course there are new features too. As usual, automatic updates will be enabled a bit later. This version is likely the last TinyWall version to officially support Windows 7. It is also the last version to support the old (v2.1) config format, a direct upgrade (without stopgaps) from v2 to future versions will not be possible. All users are recommended to upgrade. There have been a few fixes since the Release Candidate so you should update even if you already have the RC. Changelog: Code: 3.1.1 - Important update (11.10.2021.) - Add option to block internet during display power-save - Heuristically determine and show PIDs of blocked processes if possible - Support for showing and whitelisting services in Processes and Connections windows - Launch GUI with elevated privileges on boot if possible - Use exact capitalization of paths from autolearn and blocked processes - Reduce dependency on WMI and avoid polling by WMI - Avoid creation of redundant "-" entries during autolearn - Fix WFP audit logging is not disabled when autolearn mode ends - Fix "active connections" and "open ports" lists would not recognize UWP processes as such - Fix rule is ineffective if loaded while its target path is not mounted - Fix rule is ineffective for paths with certain international characters - Fix Bulgarian translation not loading - Fix non-form Korean messages are gibberish due to wrong encoding - Updated Italian translation - New Hebrew localization - GUI layout fixes for various localizations - Updated application database - Deprecation notes: Windows 7, 8, 8.1, and certain older versions of Windows 10 will soon not be supported in a future TinyWall release. Download link Patreon release post (some extra info)
TinyWall 3.1.1 on Windows 7 x86 When I launch, from start menu, TinyWall Controller multiple times, I get multiple systray instances too. Is this correct?
Yes, this is as intended, the controller should be able to run in multiple instances. For example, multiple users might be logged on at the same time and each one should be able to use the Controller. This is not new in 3.1.1 but has been like this for a long time.
OK thanks, perhaps it has helped to make the Devolo powerline adapters function better, who knows. And I haven't checked out TinyWall 3.1 yet, I always wait for some time before upgrading. Also depending on if I need the improvements or not.
Hi again, how is "Fix rule is ineffective if loaded while its target path is not mounted" supposed to work? Because for me 3.1.1. works the same as 3.0.1. If I run TinyWall on startup, then mount removable/encrypted drives and then run apps stored on them, they're unable to connect to the Internet. Opening "manage" in TinyWall and hitting apply afterwards fixes it - exactly the same as it used to be on 3.0.1.
Then it must have something to do with the volume being encrypted. It is supposed to work completely automatically. I just tried it with a non-encrypted USB-stick and it works for me. First I whitelist an executable from the removable drive, then physically remove the drive and reload the firewall. Then I insert the drive again, start the app on it and it can connect to the internet without problems. I also repeated the same experiment where I rebooted the computer with the drive removed, inserted after boot and the app on the drive could still connect. So my guess is the problem in your case has to do with encryption? Can you tell me exactly how you set up the encryption? I'll try to replicate it to solve that case too.
