From owner-freebsd-questions@FreeBSD.ORG Thu Oct 27 14:43:56 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 961AB16A41F for ; Thu, 27 Oct 2005 14:43:56 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AD9443D45 for ; Thu, 27 Oct 2005 14:43:54 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j9REhrxj002768; Thu, 27 Oct 2005 09:43:53 -0500 (CDT) (envelope-from dan) Date: Thu, 27 Oct 2005 09:43:53 -0500 From: Dan Nelson To: Yance Kowara Message-ID: <20051027144353.GA5142@dan.emsphone.com> References: <20051027142007.24881.qmail@web30312.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051027142007.24881.qmail@web30312.mail.mud.yahoo.com> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-questions@freebsd.org Subject: Re: packet forwarding X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2005 14:43:56 -0000 In the last episode (Oct 27), Yance Kowara said: > What's the difference between > > gateway_enable="YES" in /etc/rc.conf > > and > > net.inet.ip.forwarding=1 in /etc/sysctl.conf >From /etc/rc.d/routing: case ${gateway_enable} in [Yy][Ee][Ss]) echo -n ' IP gateway=YES' sysctl net.inet.ip.forwarding=1 >/dev/null ;; esac So the answer is: nothing, except that adding the line to sysctl.conf enables packet forwarding before interfaces are configured and other network variables are set, so you may get spurious "host unreachable" errors from systems trying to route through the box when it boots up. -- Dan Nelson dnelson@allantgroup.com