ThreadShield: Blocking of own IP as source

NethServer Version: 7.9
Module: ThreadShield

I have a question to better understand the behavior. I have had Thread Shield disabled for a while and only now re-enabled.
A look at the log files shows me:

Oct 10 09:33:42 ns-srv01 kernel: Shorewall:blacklst:DROP:IN= OUT=eth0 SRC= DST= LEN=700 TOS=0x00 PREC=0x00 TTL=64 ID=38601 DF PROTO=TCP SPT=2202 DPT=37480 WINDOW=227 RES=0x00 ACK PSH URGP=0

In my understanding, my server ( tries to connect an port 2202.

I can’t understand why it does that, I don’t have a dedicated connection set up or can’t remember. The port is identical to my customized SSH port. Coincidence?

I also can’t understand why Thread Shield blocks outgoing connections from my server IP.

My thread shield configuration

Information about the DST-IP IP Address Information

|ISP|Hop Off A Cloud LLC|

| — | — |
|Usage Type|Data Center/Web Hosting/Transit|
|Domain Name||
|City|Montreal, Quebec|

Am I missing something that is actually obvious?
Best regards, Marko

Ps: on the Analysis site, I can see the opposite information.

Can somebody help?

1 Like

I guess it’s just the blocked answer from your server to a host that’s listed in category Firehol level 2.

From the docs:

The Threat shield blocks connections to and from malicious hosts, preventing attacks, service abuse, malware, and other cybercrime activities using IP blacklists.

Yes, it shows the malicious IP trying to connect to your SSH port.

1 Like

Thank you for the lesson :slight_smile:

I thought that if an attacker attacked my server, the incoming connection would be blocked, not the outgoing one.

But the outgoing connection was initiated by the attacker’s attempt, well? I don’t have to suspect that a malicious program has taken root and is establishing connections to the outside world on its own?

Maybe you turned on threat shield after the attack, then the answer would be blocked.

No, I don’t think so.