Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

netscan on port 7001 and 7770 #22

Closed
mahdiyari opened this issue Feb 25, 2023 · 7 comments
Closed

netscan on port 7001 and 7770 #22

mahdiyari opened this issue Feb 25, 2023 · 7 comments

Comments

@mahdiyari
Copy link

My server got marked for abuse because of detected netscan on port 7001
It is trying a bunch of IP addresses on port 7001

@mahdiyari mahdiyari changed the title netscan on port 7001 netscan on port 7001 and 7770 Feb 25, 2023
@mahdiyari
Copy link
Author

Fri Feb 24 22:37:46 2023 TCP    49.12.242.34 4001  =>      198.18.0.6 7001
> Fri Feb 24 22:37:52 2023 TCP    49.12.242.34 4001  =>      198.18.0.6 7001
> Fri Feb 24 22:37:55 2023 TCP    49.12.242.34 4001  =>      198.18.0.6 7001
> Fri Feb 24 22:37:42 2023 TCP    49.12.242.34 4001  =>      198.18.0.7 7001
> Fri Feb 24 22:37:43 2023 TCP    49.12.242.34 4001  =>      198.18.0.7 7001
> Fri Feb 24 22:37:45 2023 TCP    49.12.242.34 4001  =>      198.18.0.7 7001
> Fri Feb 24 22:37:46 2023 TCP    49.12.242.34 4001  =>     198.18.0.11 7001
> Fri Feb 24 22:37:49 2023 TCP    49.12.242.34 4001  =>     198.18.0.18 7001
> Fri Feb 24 22:37:51 2023 TCP    49.12.242.34 4001  =>     198.18.0.18 7001
> Fri Feb 24 22:37:42 2023 TCP    49.12.242.34 4001  =>     198.18.0.19 7001
> Fri Feb 24 22:37:43 2023 TCP    49.12.242.34 4001  =>     198.18.0.23 7001
> Fri Feb 24 22:37:44 2023 TCP    49.12.242.34 4001  =>     198.18.0.23 7001
.
.
.
> Fri Feb 24 22:37:41 2023 TCP    49.12.242.34 4001  =>    198.18.1.218 7001
> Fri Feb 24 22:37:49 2023 TCP    49.12.242.34 4001  =>    198.18.1.236 7001
> Fri Feb 24 22:37:52 2023 TCP    49.12.242.34 4001  =>    198.18.1.247 7001
> Fri Feb 24 22:37:55 2023 TCP    49.12.242.34 4001  =>    198.18.1.247 7001
> Fri Feb 24 22:37:50 2023 TCP    49.12.242.34 4001  =>      198.18.2.5 7001
> Fri Feb 24 22:37:53 2023 TCP    49.12.242.34 4001  =>      198.18.2.5 7001

@mahdiyari
Copy link
Author

I confirmed this is happening when the server is running honeycomb-spkcc using docker-composer and stops when I stop honeycomb-spkcc .

@disregardfiat
Copy link
Collaborator

4001 is a port used by ipfs. I'll look thru my logs to see if i have any similar issues.

@vaultec81
Copy link
Member

Going to close in favor of these on going topics on the IPFS side: ipfs/kubo#5418 ipfs/kubo#6932

@mahdiyari
Copy link
Author

Those issues are 3 years old and will never get fixed from the looks of it.

@vaultec81
Copy link
Member

@disregardfiat Might be worth using the ipfs server profile in the docker container? I've been able to run ipfs on numerous providers with no issues (such as hetzner) for a good period of time now using that configuration.

@disregardfiat
Copy link
Collaborator

docker-compose updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants