From owner-freebsd-questions@FreeBSD.ORG Sat Oct 25 19:46:26 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AD9D16A4B3 for ; Sat, 25 Oct 2003 19:46:26 -0700 (PDT) Received: from mxsf06.cluster1.charter.net (mxsf06.cluster1.charter.net [209.225.28.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3875E43FDF for ; Sat, 25 Oct 2003 19:46:23 -0700 (PDT) (envelope-from chowse@charter.net) Received: from moe (jackson-66-168-145-25.midtn.chartertn.net [66.168.145.25]) h9Q2Fmu7027957; Sat, 25 Oct 2003 22:15:51 -0400 (EDT) (envelope-from chowse@charter.net) From: "Charles Howse" To: "'Chris Pressey'" Date: Sat, 25 Oct 2003 21:15:44 -0500 Message-ID: <001401c39b67$103a2a50$04fea8c0@moe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20031025185847.1086d7ab.cpressey@catseye.mine.nu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal cc: freebsd-questions@freebsd.org Subject: RE: Website up, then down, then up, etc. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2003 02:46:26 -0000 > On Sat, 25 Oct 2003 17:07:31 -0500 > "Charles Howse" wrote: >=20 > > Yes, the router has a web interface for configuration. It had been > > set to forward requests on port 80 to the webserver on port=20 > 80. That > > was working perfectly for over a year. I've now set it to=20 > port 8080, > > in and out, which is, of course, working. I have also enabled the > > DMZ, which, AFAIK, places the server outside the firewall, thereby > > eliminating it...? > >=20 > > Now I've told apache to listen on port 80, no joy. Change back to > > 8080, perfect! >=20 > Sorry if this is a shot in the dark, but are you sure the firmware in > your router is up-to-date? Encountered a similar case once where this > was the problem, so it might be worth checking out. Thanks for the reminder to check, but I have v.1.1 release 5, and the latest version on their website is v.1.0 release 5.