Local ISP Blocks traffic!

A local ISP has implemented restrictions on their customers without any upfront warning all in an effort to “be more secure” but what will be the impact?


In an email this morning, CarolinaNet (in downtown Greensboro) sent out this link:
http://carolinanet…details&i=18
The message states that port 135 for all traffic has been filtered at the perimeter of the CarolinaNet network…meaning it’s filtered on their equipment before it ever reaches their client’s machines.
That’s good right?
Wrong. The whole point of having machines in a facility like that is that you have the ability to serve data on any port/protocol you wish. That means that if you want to serve something on port 135 then you should be able to. This also means that it is the CLIENT’S responsibility to secure his or her own network…not the ISP’s. Normally ISPs only alert their clients to potential risks such as this one. They do not (and should not) implement restrictions and THEN send alerts as that is just bad business.
CarolinaNet also admits that it already blocks several ports and has plans for more ports to be blocked later this week.
On another point, the links in the article seem to point that the risk is only associated with Microsoft Windows servers. Even clients that don’t have windows servers that have that port exposed to the Internet or use Linux-based software which is not at risk are being restricted. This just doesn’t seem right.
This is yet another example of people taking on responsibility that is not (and should not be) their own and by doing so they are limiting the freedoms of others without justifiable cause.
It is also important to point out that other hosting facilities in the area (Bellsouth’s Business Class service, SolidSpace in Winston-Salem, DataChambers in Winston-Salem, and Inflow in Raleigh) have not blocked this traffic.