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

[Daniel L. Shipman]

I have a good friend on AT&T @Home here in Dallas (just on the edge of
Carrolton). I know from him that throttling is established at the modem
level (there are several sites to hack around this), but AFAIK this is all
that is controlled by big bubba at the modem level.

Port blocking is performed just off the local router and they have ongoing
probes testing for common ports and reporting back a list of users running
web, ftp, game ports etc.

For a while you should be fine on some weird port number, but it's only a
matter of time before they locate you and shut you down.

The whole thing comes out of a basic flaw in sharing access. The more people
who signup for the service - the slower it gets and the more you have to
police it.

Thanks for the update to your address - I'm sure that NTLUG will change it
on the website. (This said in an attempt to somehow bring my post back in
line with NTLUG requirements for on topic post)


----- Original Message -----
From: "Steve Egbert" <steve at egbert.net>
To: <discuss at ntlug.org>
Sent: Saturday, August 25, 2001 11:27 PM
Subject: [NTLUG:Discuss] McKinney AT&T @home port 80 blocked


> 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.
>
>
> Steve Egbert
> presentator of NTLUG TCI @Home Cable Modem.
>