adelphia blocking www

[deadpoint]

in apache you set "Port 8080"  in the global section and "Listen 8080" 
in the "SSL IfDefine" container for it to listen on a different port. i 
know that adelphia is blocking port 80 because myself and at least 3 
other adelphia users that i know are unable to access there websites 
when running at the default ports. but when they switch to running at 
another port the sites are accessable.

it would appear that they are only blocking port 80, every other service 
that i've tried forwarding inside works fine, ssh, https, ftp, etc.

i'm wondering at what level they are blocking traffic to port 80, 
meaning at the cable modem, or their routers. when i had the autofw rule 
setup to route traffic to port 80 i could still see SYN_WAIT  on my web 
server from the requesting client.

David Dudek wrote:

>I believe that you can also modify your web server to listen on a
>different port.  I know you can do this with Apache via the httpd.conf,
>but other smaller web servers, like tux and the LRP* web server packages,
>may work differently.
>
>I am just curious, how do you know for sure that Adelphia is blocking port
>80?  I have adelphia at home, but I don't have anything running right now
>that I can check it.  However, I do know for certain that they are not
>blocking the standard FTP port.  I would be surprised that they are
>blocking one and not the other.  It also seems silly too.  They're already
>limiting your upload speed anyhow.
>
>* Linux Router Project - see leaf.sourceforge.net
>
>  
>