| Author |
Message |
fieschko
Joined: 21 Jun 2004
Posts: 19
|
| Posted: Sat Jun 26, 2004 10:26 pm Post subject: incoming on tcp port 139 blocked or no? |
|
|
got this in my logcheck today:
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:
http://www.linode.com/products/faq.cfm :
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 ? |
|
| Back to top |
|
fieschko
Joined: 21 Jun 2004
Posts: 19
|
| Posted: Thu Jul 15, 2004 11:50 pm Post subject: Re: incoming on tcp port 139 blocked or no? |
|
|
caker ... do I misunderstand the port blocking linode does?
(Posted here since it's not so severe as to need a ticket.) |
|
| Back to top |
|
caker
Joined: 15 Apr 2003
Posts: 2392
Location: Galloway, NJ
|
| Posted: Fri Jul 16, 2004 5:50 am Post subject: Re: incoming on tcp port 139 blocked or no? |
|
|
fieschko wrote: 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 |
|
| Back to top |
|
| |
