configuration for comment bitswarm.sessions.DefaultSessionManager logs

[Sreedhar_cd]

Hi ,
How can i comment below logs .

01 Mar 2024 | 06:49:46,087 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 7, Type: DEFAULT, Logged: No, IP: 10.0.3.12:3897 } on Server port: 9933 <---> 3897
01 Mar 2024 | 06:49:46,088 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 7, Type: DEFAULT, Logged: No, IP: 10.0.3.12:3897 }
01 Mar 2024 | 06:49:46,266 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 8, Type: DEFAULT, Logged: No, IP: 10.0.1.158:64358 } on Server port: 9933 <---> 64358
01 Mar 2024 | 06:49:46,267 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 8, Type: DEFAULT, Logged: No, IP: 10.0.1.158:64358 }
01 Mar 2024 | 06:49:46,349 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 9, Type: DEFAULT, Logged: No, IP: 10.0.2.237:23364 } on Server port: 9933 <---> 23364
01 Mar 2024 | 06:49:46,349 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 9, Type: DEFAULT, Logged: No, IP: 10.0.2.237:23364 }
01 Mar 2024 | 06:49:46,607 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 10, Type: DEFAULT, Logged: No, IP: 10.0.3.12:27171 } on Server port: 9933 <---> 27171
01 Mar 2024 | 06:49:46,608 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 10, Type: DEFAULT, Logged: No, IP: 10.0.3.12:27171 }
01 Mar 2024 | 06:49:46,741 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 11, Type: DEFAULT, Logged: No, IP: 10.0.1.158:54534 } on Server port: 9933 <---> 54534
01 Mar 2024 | 06:49:46,742 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 11, Type: DEFAULT, Logged: No, IP: 10.0.1.158:54534 }
01 Mar 2024 | 06:49:46,819 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 12, Type: DEFAULT, Logged: No, IP: 10.0.2.237:12024 } on Server port: 9933 <---> 12024
01 Mar 2024 | 06:49:46,819 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 12, Type: DEFAULT, Logged: No, IP: 10.0.2.237:12024 }
01 Mar 2024 | 06:49:46,961 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 13, Type: DEFAULT, Logged: No, IP: 10.0.3.12:62288 } on Server port: 9933 <---> 62288
01 Mar 2024 | 06:49:46,962 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session removed: { Id: 13, Type: DEFAULT, Logged: No, IP: 10.0.3.12:62288 }

[Lapo]

Hi,
these are some very short-lived connections that seem to be coming from a local network.
As to why, I can't say without more details.

Thanks

[Sreedhar_cd]

Hi Lepo, Thank you reply. Iam not sure how these connection. Can you help me to debug.
Note: Just downloaded the SFS and started. No changes are made in any config files.

[Lapo]

Can you please provide more details?
Where is SFS2X installed, on your local machine?
When do these connections appear? As soon as the server is started?

The addresses shown in the logs are from the local network, so it seems that other machines in a local network are attempting to connect to your server.

Thanks

[Sreedhar_cd]

Hi Lapo,

SFS2x is installed on aws ec2.

When do these connections appear? As soon as the server is started?, yes you are correct, after starting the server these connections are appeared.

There are no other machines in my AWS account

[Lapo]

It's not clear if this is something that has happened a few times or if it's constantly happening.
It is possible that external servers are scanning an IP range and trying to connect to anything that they find, maybe searching for a vulnerable machine or something like that.

Personally I find it odd to see random connections on port 9933 since this TCP port is not very common and it's not used by other popular services. Additionally the connections seem to be coming from the local network range, which is even more bizarre, suggesting that these clients are other AWS machines.

I think there are several important bits of info missing here, but in any case this is not an issue with SFS2X but rather with your AWS setup and configuration, so I don't think we can provide further help on this.


Cheers