AIS: Integrated TRACEROUTE not possible with firewall set to PUBLIC / HIGH RISK?

Avast Free Antivirus / Premium Security
1

Hi there,

I have a Question: Is it possible to geht results with the integrated Traceroute-Application from AIS when the AIS-Firewall is set to PUBLIC / HIGH-RISK-ZONE?

In my case I don’t get any results - only one point with the IP-Adress is shown on the map (there should be a “Route” with more Points on the map when everything works ok). When setting the firewall to WORK / MIDDLE-RISK-ZONE, everything works like expected.

Is this a technical restriction or a bug?

Thanks in advance,

Timo

2

Hi, this is definitely a bug, I’ll look into it more closely and see what can we do. Thanks for the heads up.

3

Thanks for the fast answer :slight_smile:

Greetings

Timo

4

I just checked, confirming for the trace route issue when zone set to “public”, takes ages to load and in the end the map remains empty.

5

I’ll take the opportunity here for a suggestion: could you add the “who is” and “trace route” options in the log too? …means having to launch not running connections, but I find it useful…although may be technically undoable. Well, AvastUI can connect so…

6

This bug appears to back and it’s even worse now. Traceroute doesn’t even work the Home zone. When the Avast firewall is disabled, it works perfectly!

Running AIS 6.0.1203

Oh I just realized it was referring to the internal tool in AIS. I’m talking about standard tracert in Windows 7.

7

tracert (Windows) works fine here with FW set on medium (or any other mode)

8

Well it doesn’t work here and also Avast thinks it’s cool to block some internet sites when the firewall is on, with not warning or anything.

Sadly the quality of Avast has gone down quite a bit lately, they need to stop pumping broken components into it and focusing on making the core elements stable.

Guess I have to do a reinstall sigh

9

You posted in an outdated topic.
Please start a new one.

10

Nevermind, it was MBAM blocking all kind of sites which shouldn’t be blocked and reinstalling Avast fixed the tracert problem. I was missing a lot of packet rules for some reason, maybe something went wrong the update from AIS5 to 6.

11

AIS working just fine here.

12

Derp, cool story bro.