Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Ways to test web access automagically



On Mon, Jan 10, 2005 at 10:57:46AM -0500, dsr at tao.merseine.nu wrote:
> 
> On Mon, Jan 10, 2005 at 10:48:49AM -0500, David Hummel wrote:
> > On Mon, Jan 10, 2005 at 08:13:38AM -0500, Bill Horne wrote:
> > > 
> > > Unless Comcast has started to choke port 80 requests,
> > 
> > That is exactly what is happening.
> > 
> > It was like pulling teeth to get this information out of Comcast
> > tech support, but a tier 2 support person finally told me that the
> > following TCP ports are blocked:
> > 
> >   80  up  <--
> >   135 up/down
> >   139 up/down
> >   445 up/down
> > 
> > This was in September 2004.
> 
> I've been running a web server on port 80 since... 1997 on
> Comcast and its predecessors. Once there was a few days of
> blocking -- which I complained about, and shortly thereafter
> it went away.
> 
> Perhaps this is done on a neighborhood-by-neighborhood basis?

Definitely possible ... I didn't ask this question at the time.  I'm
located in the Longwood medical area of Boston.  Perhaps there was
recent abuse on this portion of the network.

-David




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org