From owner-freebsd-questions Wed Dec 8 13:26:10 1999 Delivered-To: freebsd-questions@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id A2F5615227 for ; Wed, 8 Dec 1999 13:26:07 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id NAA03942; Wed, 8 Dec 1999 13:19:24 -0800 (PST) Date: Wed, 8 Dec 1999 13:19:24 -0800 (PST) From: Annelise Anderson To: Leonard Cc: Dan Nelson , Andrzej Szydlo , questions@FreeBSD.ORG Subject: Re: NATd: tons of "failed to write packet back" errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Try changing rule 200 to 'deny log ip from any to 127.0.0.0/8' and see > > exactly what packets are tripping that rule. > > > > -- > > Dan Nelson > > dnelson@emsphone.com > > I get tons of "failed to write packet back, host is down" messages but rule 200 seems not to be causing them: 00100 198169 42253320 divert 8668 ip from any to any via ed0 00100 57140 15869434 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 65000 199035 42354731 allow ip from any to any 65535 0 0 allow ip from any to any I have tried to find information on this in the archives, and while there are quite a few ideas, no one really seems to know what might be wrong or how to figure it out. Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message