Date: Thu, 3 Aug 2000 11:56:57 -0700 (PDT) From: Archie Cobbs <archie@whistle.com> To: Shaun Jurrens <shaun@shamz.net> Cc: freebsd-ipfw@FreeBSD.ORG Subject: Re: connections via natd dying in natd Message-ID: <200008031856.LAA42218@bubba.whistle.com> In-Reply-To: <20000801011709.B4159@dakota.priv.shamz.net> from Shaun Jurrens at "Aug 1, 2000 01:17:09 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Shaun Jurrens writes: > I have been struggling with this problem for a number of months, actually. I > had it using 3-STABLE boxes and now with one 4-STABLE through the 3(.5)-STABLE > natd gateway, the same problem occurs. The problem: connections via natd > suddenly drop and similtaneously, I get errors on the console for the gateway > box that natd has "failed to write the packet back (Permission denied)". This > is almost exclusively with ssh connections (mostly because they are the most > constant long time connections I have to notice this behavior) Don't know if this is much help, but.. "failed to write the packet back (Permission denied)" almost definitely indicates that the packet being written back hit an 'ipfw deny' packet filtering rule. This is the only way that a write to a socket can generate an EPERM error. So I'd start by turining on ipfw logging for all deny rules to see which one is being triggered. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008031856.LAA42218>