incoming on tcp port 139 blocked or no?
Jun 26 13:02:26 (none) portsentry[28030]: attackalert: Connect from host: 218.89.28.60/218.89.28.60 to TCP port: 139
Jun 26 13:02:26 (none) portsentry[28030]: attackalert: Host: 218.89.28.60 is already blocked. Ignoring
Jun 26 13:02:26 (none) portsentry[28030]: attackalert: Connect from host: 218.89.28.60/218.89.28.60 to TCP port: 139
Jun 26 13:02:26 (none) portsentry[28030]: attackalert: Host: 218.89.28.60 is already blocked. Ignoring
I know that the offending ip was already blocked, but did I misread the faq? I thought that tcp:139 was blocked by linode:
The following ports are filtered for security reasons. If you need to run a specific service, run it on a different port.
[snip]
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
[snip]
or .. is it outgoing packets that are blocked but not input ?
2 Replies
(Posted here since it's not so severe as to need a ticket.)
caker
Linode Staff
@fieschko:
caker … do I misunderstand the port blocking linode does?
(Posted here since it's not so severe as to need a ticket.)
Host9 through host26 located at the Fremont datacenter do NOT have any ports blocked by the data center. The blocked ports only apply to the Dallas Datacenter.
HTH,
-Chris