Filtering Destination Unreachable ICMP messages

[tbrettallen]

I have just setup a Flare-VM with FakeNet and I am having an issue with the logs being filled with the following:

01/13/25 04:30:58 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131
01/13/25 04:31:02 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131
01/13/25 04:31:05 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131
01/13/25 04:31:08 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131
01/13/25 04:31:14 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131
01/13/25 04:31:17 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131
01/13/25 04:31:20 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131
01/13/25 04:31:24 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131
01/13/25 04:31:27 PM [ Diverter] ICMP type 3 code 1 192.168.1.131->192.168.1.131

192.168.1.131 is the machine's network address, it's on an isolated network with the gateway set to 192.168.1.1 (does not exist), and I believe these Destination Unreachable ICMPs are a result of the "internet_detector.exe"; which is making requests to unreachable destinations.

Is it possible to Filter these out of the logs?

[tinajohnson]

If you are using the executable, we don't have a config setting to control these kind of logs. If you are executing FakeNet from source code and can tweak the source code, the logging level can be set here (remember that changing the logging level would affect other logs from the DiverterBase class as well).