Date: Wed, 12 Sep 2007 11:39:06 -0500 From: Reid Linnemann <lreid@cs.okstate.edu> To: Beech Rintoul <beech@freebsd.org> Cc: Don O'Neil <lists@lizardhill.com>, freebsd-questions@freebsd.org Subject: Re: Strange port 80 access problem Message-ID: <46E8162A.7090206@cs.okstate.edu> In-Reply-To: <200709120814.48051.beech@freebsd.org> References: <015a01c7f54f$fbf04ec0$0700020a@mickey> <200709120814.48051.beech@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46E8162A.7090206>