From owner-freebsd-questions@FreeBSD.ORG Wed Sep 12 17:13:25 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1948416A41B for ; Wed, 12 Sep 2007 17:13:25 +0000 (UTC) (envelope-from beech@freebsd.org) Received: from stargate.alaskaparadise.com (137-42-178-69.gci.net [69.178.42.137]) by mx1.freebsd.org (Postfix) with ESMTP id C27F013C467 for ; Wed, 12 Sep 2007 17:13:24 +0000 (UTC) (envelope-from beech@freebsd.org) Received: by stargate.alaskaparadise.com (Postfix, from userid 0) id 200947DC5; Wed, 12 Sep 2007 09:13:23 -0800 (AKDT) From: Beech Rintoul To: freebsd-questions@freebsd.org Date: Wed, 12 Sep 2007 09:13:11 -0800 User-Agent: KMail/1.9.7 References: <015a01c7f54f$fbf04ec0$0700020a@mickey> <200709120814.48051.beech@freebsd.org> <46E8162A.7090206@cs.okstate.edu> In-Reply-To: <46E8162A.7090206@cs.okstate.edu> X-Face: jC2w\k*Q1\0DA2Q0Eh&BrP/Rt2M,^2O#R07VoT98m*>miQF9%Bi9vy`F6cPjwEe?m,)=?utf-8?q?2=0A=09X=3FM=5C=3AOE9QgZ?="xT3/n3,3MJ7N=Cfkmi%f(w^~X"SUxn>; 27NO; C+)g[7J`$G*SN>{<=?utf-8?q?O=3Bg7=7C=0A=09o=7D=265A=5D4?=@7D`=Eb@Zs1Ln814?]|k@'bG=.Ca"[|8+_.OsNAo8!#?4u MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709120913.18341.beech@freebsd.org> Cc: Don O'Neil , Reid Linnemann Subject: Re: Strange port 80 access problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Beech Rintoul List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2007 17:13:25 -0000 On Wednesday 12 September 2007, Reid Linnemann said: > 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. That's another option. I'm very lucky. Here in Anchorage, the cable provider (GCI), is totally OK with people running servers as long as you're not selling webspace or email services (Your home business is OK). They deal with abusers on an individual basis. They also do network scanning looking for bots and will put a user on security block until they fix it, but I've never known anyone who actually got blocked. I wish more ISP's had that attitude instead of trying to screw subscribers out of more money just to run their mail or website. -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/6.2R/announce.html ---------------------------------------------------------------------------------------