Regarding this: I made a Github issue. https://github.com/henrypp/simplewall/issues/274 He wont change anything. Seems like he doesn't like people who ask for improvement. Was I rude? Edit: Thank you
You weren't, this may be just a simple language barrier. henry is not very expressive in English. This may be misleading to many (not-so-advanced users, to put it like that), but there is just a need to understand how this 'logic' works. I was able to immediately tell that you should not tick the box next to the app (as was the other poster in the other thread). So this is not really a big concern. ... What puzzles me here are these multicast comms on Chrome. There are no problems allowing (or blocking) these comms when svchost is concerned (Windows services make the same comms on default install). But when it comes to Chrome, the rules simply do not work. This may be something specific to Chrome which we do not understand.
simplewall v2.3.11 (14 December 2018) https://www.henrypp.org/product/simplewall Download Changelog sha256 checksum Spoiler: Changelog v2.3.11 v2.3.11 (14 December 2018) added "/install" argument for install filtering added cache auto clean up (to prevent overflow) changed minimum size of main window (issue #269) changed installation message increased rule parsing speed (issue #276) memory optimization fixed notification window appears on taskbar (regression) fixed exclude user rules option was not working cosmetic fixes fixed bugs
simplewall v2.3.12 (25 December 2018) https://www.henrypp.org/product/simplewall Download Changelog sha256 checksum
v2.3.13 (3 January 2019) - added dns resolver caching - added dns resolver winsock fallback (issue #290) - avoid window flickering on window sizing - revert refresh filters on device arrival - fixed access rights for wfp provider and sublayer - fixed allocated strings dereferencing (issue #285) - fixed parsing hosnames with dashes (issue #271]) - fixed localization (issue #288) - fixed bugs simplewall-2.3.13-bin.zip simplewall-2.3.13-setup.exe simplewall-2.3.13-setup.sig simplewall-2.3.13.sha256
@henrypp This new version 2.3.13 seems to run a new netsh.exe command line as per my anti-exe detects when launching simplewall: Code: netsh advfirewall set allprofiles state off Is that correct and new?
Hi, If I select WhiteList mode, then all that's needed is Allowed Programs ? Meaning all other programs will be block outbound and will not be allowed to receive traffic inbound ? The bad thing I found with ZoneAlarm Free is that at first run, it recognized 56 programs, and set them to Auto. Then at next program run, it recognized 80 programs. I just wonder if this list will keep on growing. And what is going to happen when a program it does not recognize when incoming or outgoing traffic arrives. I am hoping that SimpleWall whitelist will stop everything outgoing or incoming if I don't have an allow rule.
not sure how to set my own rules, I can see user rules section but its empty right now I allow listening and loop for all for compatibility and perhaps performance reasons, allow DNS and DHCP in system rules, all blockslists are effective allowed out only for AV, browser and occasionally svhost for updates, is this safe enough?
simplewall v2.4 beta (21 February 2019) https://www.henrypp.org/product/simplewall Download Changelog sha256 checksum Spoiler: Changelog v2.4 beta v2.4 Beta (21 February 2019) new notification ui improved transactions processing added predefined rules (ftp, http etc) added option to configure 6to4 redirections (it's allowed, but undocumented earlier) added double-click for statusbar parts to make purgen faster added option to secure installed filters added more list view modes fixed notifications stay visible when special rules applied for the app fixed possible duplicate of special rules from notifications fixed multithreading and possible race conditions fixed duplicate filters callback on device arrival (issue #291) fixed dropped packets csv log delimeter fixed packages path retrieving (win8+) replaced netsh commands by com interface cosmetic fixes fixed bugs
this beta is a big improvement in information and features with enable protection of installed filters, allow IPv6 redirections 6to4 and more informative pop-up windows that shows new connections, btw. works flawlessly with eset (I know about double firewall no-no rule but this is an exeption)
because I need it, SD corrupts files under heavy load, and sometimes firewall 2, I need to make sure at least one works, it's unheard of and not typical just case specific for SD and that scenario of pc usage. They do not interfere badly, sometimes delays (not confirmed what is causing them) but generaly fast speeds and no spotted problems, also eset hips would protect simple wall. SW seams to have precendence over Eset when a new connection is found, so first click allow\deny on SW then on Eset. Other solution is using SD without connecting.
simplewall v2.4.1 beta (1 March 2019) https://www.henrypp.org/product/simplewall Download Changelog sha256 checksum
I am trying out Simplewall 2.3.13. If I disable windows firewall and use just Simplewall and scan my PC from elsewhere on my home network (Using Fing on a tablet) I find port 135 open and I don't know why. I have the following rules:
simplewall v2.4.2 beta (5 March 2019) https://www.henrypp.org/product/simplewall Download Changelog sha256 checksum
tcarrbrion, I think WS-Discovery includes port 135 which is used by NetBIOS. Seasoned network admins are not bothered by it, as they allow NetBIOS, an old protocol, to roam their network. But SMB v1 is also an old protocol, used by File and Printer Sharing since the XP days, and there is a hidden security flaw, all through the years. And it was exploited by Wanna Cry ransomware to its massive success. So, I don't trust old stuff just because it has be sticking around for a long time. If you don't have shared folders in your network, then ban that protocol. The principle for configuring firewalls is DEFAULT DENY.
simplewall v2.4.3 beta (9 March 2019) https://www.henrypp.org/product/simplewall Download Changelog sha256 checksum
Thanks. It's not the ws-discovery. Unticking all the protocols still leaves port 135 open. Looks like a bug in Simplewall to me. It is closed if I used Simplewall plus Windows firewall.
simplewall v2.4.4 beta (15 March 2019) https://www.henrypp.org/product/simplewall Download Changelog sha256 checksum
