[NTLUG:Discuss] McKinney AT&T @home port 80 blocked

[Stephen Denny]

AT&T began "indefinitely" blocking port 80 to slow down the infection rate 
of the code red virus.

It took businesses about a week to clean up from code red.  After that the 
huge majority of attacks were clearly originating from consumer broadband 
connections.  You can imagine the traffic load this was causing as tens of 
thousands of @home customers webservers started scanning outbound.  
Unfortunately, blocking inbound was a little late, as so many machines had 
already been infected, but I'm sure it helped stem the tide somewhat.

This port 80 blocking began about 3 weeks ago, but it doesn't seem to have 
been universally implemented across the country yet.  AT&T did issue a 
statement regarding it.  Sorry I don't have a link handy.

As I recall, the statement said that these ports were not needed for the 
consumer service they were selling.  My guess is they will use this 
opportunity to permanently block inbound port 80 (web) and 25 (mail).

Regards,

Stephen Denny


>From: "Steve Egbert" <steve at egbert.net>
>To: <discuss at ntlug.org>
>Subject: [NTLUG:Discuss] McKinney AT&T @home port 80 blocked
>Date: Sun, 26 Aug 2001 01:27:58 -0500
>
>Much to my chagrin, my IP's port 80 is blocked for McKinney1 neighborhood
>(mckiny1.tx.home.com).  I'd like NTLUG'r website maintainer to add ":81" to
>my URL in the NTLUG Calendar until I fix this.
>
>I'd like to know if there is any other AT&T @Home users in the DFW that 
>have
>their port 80 blocked or not, particularly McKinney.
>
>I'm beginning to wonder if AT&T NOC (Network Operation Center in Denver, 
>CO)
>is selectively modifying each user's DOCSIS cable modem to block port 80 or
>if the block is on a subnet basis typically at the neighborhood router 
>edge.


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp