|
|
#1
October 8th, 2011, 10:50 PM
|
|||
|
|||
Apply ICMP Filter
Hi. We have a situation that mirrors brady747's Apply ICMP Filter thread. That thread was too old to reply to, so I am starting this one.
In essence, we have communication being stopped by ESET's firewall, and the firewall log shows the following:
We can replicate it very easily by pinging from the client machine to the machine running ESET firewall. If we completely disable the ESET firewall (Advanced setup... -> System integration -> Personal firewall is completely disabled), the communication goes through without a hitch. There are a number of rules / settings labeled "ICMP", and we've tried to disable / circumvent all of these, but still the communication is blocked. In short, ESET firewall is applying some rule / filter that is described by the ESET firewall in its log as "Apply ICMP filter". There is only one (1) defined rule [an ESET default rule] using the ICMP protocol, and there are no defined rules that indicate an "ICMP filter". What is this rule / filter that ESET firewall is applying, and how can it be disabled (without disabling the firewall)? Is this some internal communication control that users cannot alter? In the aforementioned thread, Marcos indicated "If a communication is being blocked and you need to figure out the rule that is blocking it . . . [t]his should give you enough information to adjust the necessary rule." In general that is true. However, in this case we cannot determine from the information provided by the ESET firewall (above) the rule that should be adjusted, let alone how "to adjust the necessary rule". Can anyone shed light on what ESET firewall is doing to prevent the communication, and how to keep ESET firewall from blocking it? . Last edited by AVPro : October 9th, 2011 at 01:33 AM. |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|
