Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Aug 1999 07:30:50 -0700
From:      "Mr. Kasey A. Hohenbrink" <kasey@HoHenBrink.NET>
To:        beemern@ksu.edu, "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG>
Subject:   Re: [Fwd: Solution for: natd[130]: failed to write packet back  (Permission denied)]
Message-ID:  <37C6A11A.7E35836C@hohenbrink.net>
References:  <37C2CCCE.9B69E233@hohenbrink.net> <37C2D1B2.2BC8E026@ksu.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
All,

Per my earlier email, this problem seemed to be caused 
by the interaction of natd and ipfw.  It really looks 
like that natd reports this error when it cannot write
the packet back for any reason - duh - sometimes I really
overstate the obvious.

I have seen two different scenerios for the error,

	1.  ipfw rules on the natd interface that deny
		the packet.
	2.  routed reports that the route is down and
		won't accept the packet. (as shown
		below in the attached post)

		this error is generally a slightly 
		different message.  Host down, network
		unreachable.

Kasey

beemern@ksu.edu wrote:
> 
> "Mr. Kasey A. Hohenbrink" wrote:
> 
> > I was wrong, it didn't work.  Any suggestions?
> >
> > Kasey
> >
> > -------- Original Message --------
> > Subject: Solution for: natd[130]: failed to write packet back
> > (Permission denied)
> > Date: Tue, 24 Aug 1999 09:42:57 -0700
> > From: "Mr. Kasey A. Hohenbrink" <kasey@hohenbrink.net>
> > To: freebsd-questions@FreeBSD.ORG
> >
> > Hey,
> >
> > Have you guys seen this error message before.  Especially
> > at home when connected to a DSL or Cable Modem?
> >
> > Aug 24 08:07:50 gw natd[130]: failed to write packet back (Permission
> > denied)
> > Aug 24 08:08:11 gw last message repeated 3 times
> > Aug 24 08:10:11 gw last message repeated 5 times
> > Aug 24 08:17:45 gw last message repeated 11 times
> >
> >
> 
> i have a fbsd box setup as a bridge/firewall at my work on a college
> campus.
> 
> i get this exact same error if i disconnect the network cable from my
> Outside Interface
> 
> i'd say check to make sure your route table is setup correctly and also,
> if you are using ipfw, check your rules to make sure they aren't
> restricting your network traffic too tightly and giving a "permission
> denied" error
> 
> i don't know exactly WHAT causes it , or WHY it gives that error if i
> disconnect from the "outside" but i just thought this might help some.
> 
> good luck!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37C6A11A.7E35836C>