From owner-freebsd-questions Tue Apr 23 11:41:12 2002 Delivered-To: freebsd-questions@freebsd.org Received: from sage-one.net (adsl-65-71-135-137.dsl.crchtx.swbell.net [65.71.135.137]) by hub.freebsd.org (Postfix) with ESMTP id 7F9C837B404 for ; Tue, 23 Apr 2002 11:41:08 -0700 (PDT) Received: from SAGEONE (sageone [192.168.0.5]) by sage-one.net (8.11.6/8.11.6) with SMTP id g3NIf6I01034; Tue, 23 Apr 2002 13:41:06 -0500 (CDT) (envelope-from jack@sage-one.net) Message-Id: <3.0.5.32.20020423134104.02632078@mail.sage-one.net> X-Sender: jack@mail.sage-one.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 23 Apr 2002 13:41:04 -0500 To: Nick Rogness From: "Jack L. Stone" Subject: Re: Routed daemon Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.20020423074949.011fa098@mail.sage-one.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 12:08 PM 4.23.2002 -0500, Nick Rogness wrote: >On Tue, 23 Apr 2002, Jack L. Stone wrote: > >> At 12:10 AM 4.23.2002 -0500, Nick Rogness wrote: >> >On Mon, 22 Apr 2002, Jack L. Stone wrote: >> > >> >> Running FBSD 4.5-release > >[SNIP] >> > >> > You need to forward packets between interfaces which can be >> > accomlished by setting: gateway_enable="YES" in /etc/rc.conf >> > and reboot. >> > >> > You can check the status of it by: >> > >> > # sysctl net.inet.ip.forwarding >> > net.inet.ip.forwarding: 1 >> > >> > It should say 1 not 0. >> > > > >> Hi, Nick: It indeed says "1"...... but, I do not have the routed >> daemon set in rc.conf and wondered if this was the problem. Also, >> server #2 is set to look to server #1 as the defaultrouter, but I do >> not have gateway enabled on server #2... should it be...?? ...and >> should the routed daemon be enabled to solve this barrier >> problem....?? I'm just missing some simple setting and looking for >> anything.... > > > No, server #2 is not forwarding packets between interface and no, > routed will not help you (probably). > > Man! Do I feel foolish! It was NOT a problem after all. If I go to another computer not on my own network, it brings up the webserver #2 just as it is supposed to. The packets ARE being forwarded properly from server #1, but trying https://www.asafeserver.com (server #2) from my own station on the LAN kept going to the main server #1 instead. So, I had a friend in California (I'm in Texas) try the new server and it came right up... soooo, I was trying to solve a problem I never had...!!! Ouch! What a waste of time! Thanks for the help anyway..... .... our website: http://www.sage-one.net/ Best regards, Jack L. Stone Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message