I’m trying out NetVeda Safety.Net firewall and have a couple of questions.
Firstly, I’m getting the old problem of avast needing permission to access the net after every update which I’ve had with a couple of firewalls in the past but, after some searches, I haven’t noticed any other people having this with NetVeda.
Secondly, I get quite a lot of warning pop-ups that the webshield is being blocked from connecting various restricted ports such as 1900, 445 etc but I only have webshield set to scan ports 80, 81 and 443. Does anyone know why webshield would be trying to connect to these ports? I use a fair few security apps and I’m 99.9% certain I don’t have any trojans or anything.
I believe there have been a few threads relating to NetVeda so I would suggest a forum search.
I can’t see how web shield is being blocked as it doesn’t scan those ports. Other than NetVeda not being able to monitor the program attempting to use the local proxy of web shield in a similar way to the local proxy loopback issue with Sygate, where the only way for it to work was not to use the transparent proxy of web shield but to manually set your browser to use the a proxy localhost, port 12080.
As David R wrote, Web Shield uses local port of 12080. So, I presume that you meant remote ports. As far as I know, port 1900 and 455 are popular intrusion route. Are you sure your computer hasn’t been taken by a bot?
Web Shield is designed for HTTP port not HTTPS port. It is useless to let Web Shield scan port 443 since the port is not designed to be read from outside.
Ok first up, thanks for the info on port 443. I do remember reading that some time ago but it must have slipped my mind.
After more searching of the forums and google I still didn’t find similar problems relating to NetVeda but after some more detailed inspecting I’ve found answers to the problems.
First problem, regarding being asked for permission after an avast update. When asked if I want to allow I had been selecting to allow always but for some reason in the NetVeda app trust settings it keeps showing as ask, rather than allow. After changing it manually in the trust setting, avast updated itself earlier without NetVeda asking. Problem solved.
Second problem, this has turned out to be cock-ups on my part, as so many problems turn out to be. I had rules set to block the more dangerous ports but I had only half set them up so ports like 1900 were being blocked to all protocols and all directions and avast webshield was actually being blocked from using local port 1900 when connecting outbound. I couldn’t find any record of it being blocked to port 445 so I really don’t know where I got that from. Another mistake. I really should get more sleep.
It has been a journey but you have learnt something in the process and so have we. Interestingly I found about 15 hits (including this one) on the forum search for netveda in the avast 4 home/pro, general and off-topic forums. It also goes under the name Safety Net I believe.
Errr…fannymites seems to have the firewall block even Web Shield loopbacks, which is not helped by the search but spending time with firewall apps. Yes, I myself made a lot of unbelievable mistakes before I became accustomed to Kerio.
It is good that there was nothing serious, in any case.
If you see my posts at Wilders, I have been one of the early users of NetVeda, sadly, this promising app has gone the Jetico way with no updates, it does have problems with Avast transparent scanning as well as updates, I stopped using it months back as anything that doesn’t work with Avast is out of my system. Even the new ZAP6 gave me problems, Avast Web Shield as well as mail scanning stopped functioning so out it went from my system. The older version 5.5 ZAP although did not give me this problem. In your case, I would advise you to try out other firewalls.
Then, this is what DavidR mentioned. I missed to read his edited post. :-[
And Zone Alarm Free, I guess…and as DavidR wrote in the edited post, the loopback problem with Sygate (and Netvida) virtually disables the user to use Web Shield as a transparent proxy server.
Unfortunately, the lack of the number of firewall apps which can be used with Avast is a downer for Avast. Alternatively, you might like to stop using Web Shield, though.
There is nothing stopping NetVeda’s use with avast, you only need to manually set your browser to use the web shield proxy and don’t use the transparent proxy of web shield as I mentioned in that post.
Unfortunately, the lack of the number of firewall apps which can be used with Avast is a downer for Avast. Alternatively, you might like to stop using Web Shield, though.
My reply was more related to your comment as it doesn't mean you can't use a firewall with avast, just that you would have to set up some of them not to use the transparent function of avast (just as non-NT based OSes have to) and set your browsers proxy to use web shield. You don't have to disable web shield.
Sorry, forget to mention it. ZA free works perfectly with avast! and WebShield.
I don’t think there are such few firewalls for that. Proxy - firewall - antivirus programs have issues each other. Sometimes is due to avast! but a lot of times is the other part. In this case, ZoneLabs driver conflict was never corrected by them. It’s well known the problem is there and not here.
As far as I aware not it doesn’t lower your security as you are still able to use web shield, just that you have to configure your browser to use it (not too difficult). It is certainly more secure than leaving the transparent proxy of web shield on when the firewall can’t differentiate between the program using the web shield local host proxy. It is much more secure than disabling web shield completely.
I came back to Sygate, even though it has the proxy issue, from Kerio 2.1.5, 2 days ago. I feel actually a bit safer with SPF than Kerio 2.1.5.
Heard so much of BSODs that could come with Kerio, I became a bit wary.
But in my experience it was a really good firewall.
It forgot it’s settings when I accidentally ran it with SP2 firewall together, but never otherwise.
But forgetting it’s rules, they were the allow ones, so I was still safe
It was a good experience.
As long as you don’t use transparent proxy setting and configure your trusted browsers to avast WebShield only, it is a well behaved local proxy with SPF and I guess NetVeda too
Tech, my words were about my Kerio 2.1.5 experience, and as I said not much bad experiences expect with it. Only loosing rules and needing to load them back. An easy thing to do btw.
It was a side topic mention.
So Kerio 4.2.1 should not be commented by you. I have no experience with it. Happy you like it
I am not into firewall arguments, but you never understand
I posted mine cause the transparent proxy topic came out. And seems common with both Sygate and Netveda that they have local proxy issue.