Project

General

Profile

Actions

Bug #3830

closed

My friend scanned my network for open ports and even though I don't have a rule for ports 525,853, 48976-49127 but activity on my network was picked up...

Added by James Morgan about 11 years ago. Updated about 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/28/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1.x
Affected Architecture:

Description

ugh this might be a severe problem so I'll do my best to explain and the problem can be replicated on v2.1.4 only.

My friend scanned my home network: 99.250.154.21 from his home network for open ports, for some reason TShock for Terraria picked up the scan as an attempt to connect to the server!? https://www.dropbox.com/s/azvhd6lscruc7ha/Screenshot%202014-08-28%2023.26.51.png?dl=0

Only ports 525,853, 48976-49127 were affected but none of those ports have a configured NAT or firewall rule!

https://www.dropbox.com/s/k45e9kgw1yyciee/Screenshot%202014-08-28%2023.30.23.png?dl=0

I have the RFC1919 and Na/IANA rules... https://www.dropbox.com/s/8dbgvdd2kyyt35d/Screenshot%202014-08-28%2023.31.28.png?dl=0

So essentially those ports are open to the net? I imagine if a service was running on one of those ports, it would be bad news!

Actions #1

Updated by jeroen van breedam about 11 years ago

I scanned 99.250.154.21 using Nmap.
result: All ports are filtered, none are open (thus OK)

Actions #2

Updated by Jim Pingle about 11 years ago

  • Status changed from New to Rejected

You can start a thread on the forum to discuss, but there likely isn't a bug here. Those ports could have been opened by UPnP.

Actions

Also available in: Atom PDF