Date: Thu, 27 Jan 2000 11:33:31 +0100 From: Sameh Ghane <sameh@fr.clara.net> To: Brett Glass <brett@lariat.org> Cc: security@FreeBSD.ORG Subject: Re: Riddle me this Message-ID: <20000127113330.A34644@noc.fr.clara.net> In-Reply-To: <200001270355.UAA01355@lariat.lariat.org>; from brett@lariat.org on Wed, Jan 26, 2000 at 08:55:50PM -0700 References: <200001270355.UAA01355@lariat.lariat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Le Wed, Jan 26, 2000 at 08:55:50PM -0700, Brett Glass écrivit: > 00049 deny ip from 224.0.0.0/4 to any via any > 00050 deny ip from any to 224.0.0.0/4 via any > > So far, so good. But a couple of days later, when I checked the logs, I saw: > > Jan 26 15:23:49 victim natd[125]: failed to write packet back (No route to host) > > Maybe I'm just dense this evening and the cause of the message is obvious, but > I can't figure out what would have generated this message. The system has a > static default route to the upstream ISP's router. > > Is this a side effect of the rules I added? Or of something else? No, you would have get a "Permission denied" error message. Try to hack /usr/src/sbin/natd/natd.c and especially the 'FlushPacketBuffer' function to see which IP adress are implicated. -- Sameh Ghane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000127113330.A34644>