From owner-freebsd-questions@FreeBSD.ORG Sun Oct 26 15:25:39 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 ABB4316A4B3 for ; Sun, 26 Oct 2003 15:25:39 -0800 (PST) Received: from mxsf20.cluster1.charter.net (mxsf20.cluster1.charter.net [209.225.28.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B287943FAF for ; Sun, 26 Oct 2003 15:25:38 -0800 (PST) (envelope-from chowse@charter.net) Received: from moe (jackson-66-168-145-25.midtn.chartertn.net [66.168.145.25]) h9QMYUlA069348; Sun, 26 Oct 2003 17:34:34 -0500 (EST) (envelope-from chowse@charter.net) From: "Charles Howse" To: "'Matthew Seaman'" Date: Sun, 26 Oct 2003 16:34:28 -0600 Message-ID: <000701c39c11$51c30be0$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 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal cc: 'Don Tyson' 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 23:25:39 -0000 > > > > It certainly is perplexing. > > =20 > > > It is, isn't it? > >=20 > > Yes. I've had similar impossible problems in the past. One time it > > turned out to be a broken network cable, and the other time it was > > just my inability to fathom the somewhat obscure way a particular > > device implemented packet filtering. Once you know what the answer > > is, you'll wonder how it took you so long to realise something so > > obvious... >=20 > Been there, done that, got the T-shirt. :-) > I'm currently installing Apache2 on larry, the secondary FBSD=20 > machine to see if it works from there. > That should give me a clue, and won't hurt anything at all. Well, it's working now, but I don't know why. :-0 I unplugged the Cable Modem and Router overnight while I was at work. When I got home from work this morning, I installed Apache2 on larry, and configured the router to forward to larry on port 80. No joy. I reset all the router options to the defaults, and set up the port forwarding. No joy. Later, I decided to try and bypass the router by connecting curly (the original webserver) directly to the Cable Modem. I set curly for DHCP and rebooted, but it couldn't get an IP address (I probably didn't configure it right), so I set it back the way it was originally, and rebooted. Now it's working. 22:30 UTC.=20 Mother used to tell me, "Stop stomping around in the kitchen! I'm baking a cake, and it will fall." I'm going to walk very softly for a while.