Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Dec 1999 13:19:24 -0800 (PST)
From:      Annelise Anderson <andrsn@andrsn.stanford.edu>
To:        Leonard <leonard@mofo.theta-chi.net>
Cc:        Dan Nelson <dnelson@emsphone.com>, Andrzej Szydlo <andrzej@gv.edu.pl>, questions@FreeBSD.ORG
Subject:   Re: NATd: tons of "failed to write packet back" errors
Message-ID:  <Pine.BSF.4.10.9912081316040.3924-100000@andrsn.stanford.edu>
In-Reply-To: <Pine.BSF.4.10.9912080832030.18321-100000@mofo.theta-chi.net>

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

> > 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9912081316040.3924-100000>