View Single Post
Old 23-11-2003, 14:58   #44
Myron
Inactive
 
Join Date: Nov 2003
Location: Planet Earth
Posts: 49
Myron is an unknown quantity at this point
Re: More port blocking

Here is an RFC:

NTL could do with blocking inbound connections to port 17300. It seems the hackers are trying to get their revenge. My router is recording quite an increase in connection attempts to TCP port 17300 from various IP addresses.

The problem is that port blocking is not really an answer. There will come a point where so many ports will be blocked that it will be becoming impossible to use the Internet.

I was rediculed for the suggestions some months ago, but really NTL should upgrade their UBR's or firewalls so the customer has some basic contol over what can connect to his/her equipment.

By default every inbound port should be blocked. This would not be a problem because reply ports will not be blocked. Routers already so this and have been doing this for years. Un-educated users, I think, would not touch these options. 'cos they don't know how it all works.

The customer would be given three simple options that can be changed at any time.

Option 1: Block all inbound connections, unless to a reply port.
Option 2: Block all inbound connections selected by NTL.
Option 3: Block all inbound connections only for ports 135, 137, 139 and 445.

Any customer that would select option 3 would automatically be put on NTL's watch list so any suspicious traffic would be looked by at NTL's network operations centre and appropriate action taken.

Just three simple filter sets that can be defined network wide and each customer could choose only one of them. You would not want to allow the customer to define their own filter sets as then it will be totally unmanagable and the memory and processing power of the router might now be enough.

The option suggested here would work as it already implemented as option 3 in the suggestion above.
Myron is offline   Reply With Quote