From owner-freebsd-questions Wed Oct 3 13: 0:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id 4850D37B403 for ; Wed, 3 Oct 2001 13:00:49 -0700 (PDT) Received: from dialup-209.247.136.53.dial1.sanjose1.level3.net ([209.247.136.53] helo=blossom.cjclark.org) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.32 #2) id 15osBW-0000N2-00; Wed, 03 Oct 2001 13:00:42 -0700 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id f93Jx5d09112; Wed, 3 Oct 2001 12:59:05 -0700 (PDT) (envelope-from cjc) Date: Wed, 3 Oct 2001 12:58:49 -0700 From: "Crist J. Clark" To: Nick Rogness Cc: Chip , freebsd-questions@FreeBSD.ORG Subject: Re: natd permission denied at bootup Message-ID: <20011003125849.A8391@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <0110030627070H.96094@chip.wiegand.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from nick@rogness.net on Wed, Oct 03, 2001 at 02:25:30PM -0500 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 On Wed, Oct 03, 2001 at 02:25:30PM -0500, Nick Rogness wrote: > On Wed, 3 Oct 2001, Chip wrote: > > > On Wednesday 03 October 2001 01:29, Crist J. Clark wrote: > > > On Tue, Oct 02, 2001 at 10:22:48PM -0700, Chip wrote: > > > > > > [snip] > > > > > > > natd: failed to write packet back (permission denied) > > > > routed: send bcast sendto(xl0): permission denied > > > > starting final network daemons: firewall, routed: sendto(dc0): > > > > permission denied. > > > > > > This sure looks like your firewall not passing packets. And we can > > > fix the routed(8) problem easily. You don't need it, turn it off. > > > > > I disabled that line, but am still getting the message: > > natd: failed to write packet: no route to host > > Well, look at what it says "no route to host"...you either don't > have a default gateway set or you can not reach that network for > some reason. Looking again at your usual firewall configuration, Chip, there seems to be a problem. rc.conf(5) has, > > > > ifconfig_dc0="inet 66.114.152.128 netmask 255.255.248.0" But you have, > > > > # Outside nic > > > > oif="dc0" > > > > onet="66.114.152.0" > > > > omask="255.255.255.128" > > > > oip="66.114.152.128" In rc.firewall. Note the change in the mask. Your IP, 66.114.152.128, does not actually reside on the network you specify, 66.114.152.0/25. This would make the gateway unreachable. As for why things don't work when you put in the completely open firewall rules, that I do not understand. Are there any other customizations in your start up? Suspicious error messages? Once things are up, ping a host on either side of the gateway and then get the output of, # ipfw show # ifconfig # netstat -rn # ps auxww | fgrep -e natd -- Crist J. Clark cjclark@alum.mit.edu cjclark@jhu.edu cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message