On 9/12/07, Reid Linnemann <[EMAIL PROTECTED]> wrote:
> Written by Beech Rintoul on 09/12/07 11:14>>
> > It's very possible that your ISP is blocking port 80. It seems more
> > and more of them are doing that with home subscribers. I know someone
> > who has service with one of the large telcos and they not only block
> > port 80, but mail and ftp as well. They told him if he wanted to run
> > servers he would have to subscribe to business service at 5X the cost
> > of residential.
> >
> I've had a similar experience with COX Communications in the US midwest.
> They block http, https, alternate http ports like 8000 and 8080, smtp,
> and I think pop and imap/imaps. I'm sure part of the reason for this
> paranoid behavior is to protect their networks from saturation from bots
> and whatnot, but part of me thinks they just want to stick it to their
> customers whom they view as pesky annoyances rather than valuable
> consumers. I circumvent these hassles by boring ssh tunnels to the
> services I need access to on my home machines. This is a stopgap until I
> get time to fiddle with openvpn.

It might depend where  you are on their network, but there's some
inconsistencies with the blocking. Port 80 is blocked, but port 443 is
allowed. Port 25 is blocked, but 587 is allowed. 135, 137, 139, and
445 are blocked. 8080, 8081, and 10000 get through to my network. Most
"other" ports are allowed by default.

Like it or hate it, it's a control designed to support their
subscriber AUP, which states pretty plainly that customers are
forbidden to "host servers" on the home user accounts
(http://www.cox.com/policy/  #6). Business lines have such
restrictions listed and allow hosting services by policy, and puts the
burden of "security" on the customer rather than attempting to enforce
by technical means.

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to