adelphia blocking www

[Charles Rishel]

Well.. heres a bit of info.. I used to work at Adelphia.. so I can most 
definitely confirm that they are blocking port 80.. they do it at the modem 
level.

The primary reason for doing this..
1.  PLink is sold as 'residential' use.. and therefore they feel that a 
residential user has no need to host their own websites from home.
2.  I was working there when code red was flooding the net.. you should 
have seen how many users are running MS web servers at home.. the constant 
traffic threatened to wipe out ALL connectivity in a good many areas.. This 
sped up the implementation of blocking port 80.. although they were 
planning to do that anyway.
3.  Yes.. they can/will charge for 'additional' services if you request a 
'business' account.. even though (if I remember correctly) they still don't 
want you to run a server on the connection.  Doesn't make much sense to 
me.. but then again.. Adelphia never did make much sense.

I noticed a couple of people suggesting that you change your server 
settings to accept port 8080 as a connection port.. this is all well and 
good, but doesn't really solve your initial issue, as  you are redirecting 
traffic from your router to the server.. so you can leave the configs alone 
unless you have specific reason for changing it.

Now.. as I stated.. You should be able to redirect traffic from external 
sites using the port number after the link as I mentioned.. but this won't 
help with people coming directly to your box from a DNS record.. as all 
http traffic is by default sent to port 80.. which of course your modem 
will block.

My suggestion.. setup a single page somewhere online.. and then redirect 
traffic to your home machine.. making sure that the link is active whenever 
your IP may change.

Not that I advocate breaking the rules.. but hey.. this is the age of 
information.

Chaz03

At 09:03 PM 7/21/03 -0700, you wrote:

>--- deadpoint <deadpoint at adelphia.net> wrote:
> > hello,
> >
> > i've noticed that adelphia is blocking traffic to port 80/http so people
> > can't connect to personal webserver running inside there network. so i
> > figured that i'd do a little port forwarding to get around this yet i'm
> > still unable to get to my site. now i don't think that i have anything
> > misconfigured in the ipchains rules but i'm look for some clarification.
> >
>
>That's correct,  they also block a handful of other ports as well.
>
> > i'm run coyotelinux 1.3.something with kernel 2.2.19. i've flushed all
> > existing ipchains rules and ipmasadm rules so all i have is the 1 portfw
> > rule. the site is www.darins.net
> >
> > coyote# ipmasqadm portfw -a -P tcp -L `getifaddr eth1` 80 -R 192.168.0.3
> > 6000
> > coyote# ipmasqadm portfw -l
> > prot 
> localaddr            rediraddr               lport    rport  pcnt  pref
> > TCP  ny-niagara6a-b-23.buf.adelphia.net 192.168.0.3
> > www     6000    10    10
> >
> > any ideas or thoughts on this?
> >
>
>One way to see if the rule worked, is to run nmap from the outside of your
>host. (neighbor, work, school, etc..)  don't portscan adelphia's servers 
>though
>as I think it's against their terms of service (though they can scan you
>anytime...  nice rules eh? )
>
>
>=====
>Dave J. Andruczyk
>
>__________________________________
>Do you Yahoo!?
>Yahoo! SiteBuilder - Free, easy-to-use web site design software
>http://sitebuilder.yahoo.com

"If you want others to follow, give them leadership that they can believe in."