From owner-freebsd-bugs Thu Jun 3 14:40: 5 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 322D3158C6 for ; Thu, 3 Jun 1999 14:40:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA42993; Thu, 3 Jun 1999 14:40:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 3 Jun 1999 14:40:03 -0700 (PDT) Message-Id: <199906032140.OAA42993@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: mitch@hardwarestreet.com Subject: Re: kern/11766: Can not traceroute through ipnat. Reply-To: mitch@hardwarestreet.com Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/11766; it has been noted by GNATS. From: mitch@hardwarestreet.com To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: kern/11766: Can not traceroute through ipnat. Date: Thu, 3 Jun 1999 14:32:23 -0700 (PDT) I've looked at the FreeBSD 3.2 and the older release of ipfilter still seems to be what the kernel is being built with. That release, which is in /usr/src/contrib, is quite old and has a number of bugs including the one which I am reporting in kern/11766. Are there plans to integrate the current ipfilter release into FreeBSD like this older one has been? Is there someone already responsible for doing this? If not, I could possibly see if I can get it into my current schedule... ~mitch /* gnats-admin@freebsd.org [gnats-admin@freebsd.org] writes: */ >Thank you very much for your problem report. >It has the internal identification `kern/11766'. >The individual assigned to look at your >report is: freebsd-bugs. > >>Category: kern >>Responsible: freebsd-bugs >>Synopsis: Can not traceroute through ipnat. >>Arrival-Date: Tue May 18 12:20:01 PDT 1999 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message