![]() This later option may be the better balance. I am sure it would be possible for the team to add some facilities such that you either store less information or perhaps allowing some granularity to be wiped after a certain period of time. I guess you could say that logs are a little like insurance policies in that you hope that you do not need them but …. It keeps quite a detailed amount of information in a fairly compact way because the big problem with logging is that the user does not necessarily know what they need until something happens and even then they may need completely different information than they did on a previous occasion. Glasswire tries to be as flexible as possible in what it does and the way it does things. It’s mainly the firewall functionality that I’m using, and I find that once you actually have a list of hundreds of applications, it starts to become unmanageable for that purpose with no search/sort options or automatic block/ignore/allow rules. Maybe GlassWire just isn’t the program for me? I only really need a generalized look at how much bandwidth an application has used each day this week, then four weekly averages and monthly averages after that, not being able to see every single connection an application has made to the minute from months ago. I don’t know what the solution is, but I find that I don’t need the highly specific information that GlassWire is logging all the time. ![]() I suspect that applications which are making lots of small connections are causing this. I’ve also had problems with GlassWire’s log files ballooning in size - often to tens of GB and having to manually clear them every month or so. So, it stands to reason those who do that would do so for 1528×199 12.6 KB Traffic for nisserv.exe on my other four systems is not blocked.Īnyhow, I just found the ratio interesting vs that of SmartScreen and not a scrutiny of any issue because Microsoft Defender Antivirus Network Inspection Service can be disabled for those with privacy/telemetry concerns. That's typical of the traffic observed in v2 over the years. Since this system was updated yesterday, what I have is today's v3 data for nissrv.exe which is so far 9.5/175.9 KB U/D of traffic with. Which version of GW v2.x that implemented that can be discovered if anyone cares to dig into that. Following versions of nissrv.eve received the "kernel" icon and a "can't be blocked" OK dialogue box. 6 on the system I'm using now) that could be toggled was. ![]() The last version of nissrv.exe (currently. The US1 region address isĪnd there's another address for the EU1 region which is I don't know.Ĭlick to expand.By this you mean Microsoft Network Realtime Inspection Service got moved from Active Apps to Blocked Apps? UPDATE: GW v3.0 users at 2187 and climbing fast.īTW One can login to the portal at any time on a browser and log out without disturbing the endpoint(s) or one's account data/status. There were a little less than 1100 beta testers, so it would appear that almost 700 users have upgraded and are logged in. Compare that to 1286 out of 1770 for Windows Defender SmartScreen. Interesting that only 33 out of 1770 GW users are using Microsoft Network Realtime Inspection Service (nissrv.exe). Prior to that, I restarted the systems and waited about an hour for each v2.3.449 just sat there. The other three needed the v3.0 setup.exe for installing over v2.3. My E8400 Win10 Pro which was running the beta and my i5-2430 Win7 Home Premium, both performing the update when the systems were brought out of hibernation. Oddly, two of the systems updated themselves. No issues all configs/settings/data saved. All five of my systems got updated to v3.0.474 from v2.3.449 and all represent correctly in the console as Legacy-Elite.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |