From owner-freebsd-current Thu Aug 22 14:22:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18795 for current-outgoing; Thu, 22 Aug 1996 14:22:36 -0700 (PDT) Received: from red.jnx.com (ppp-206-170-2-68.sntc01.pacbell.net [206.170.2.68]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18784; Thu, 22 Aug 1996 14:22:32 -0700 (PDT) Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.5/8.7.3) with ESMTP id OAA03962; Thu, 22 Aug 1996 14:22:27 -0700 (PDT) Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.5/8.7.3) with ESMTP id OAA05175; Thu, 22 Aug 1996 14:22:16 -0700 (PDT) Message-Id: <199608222122.OAA05175@base.jnx.com> To: Julian Elischer cc: sos@freebsd.org, "Rodney W. Grimes" , current@freebsd.org, archie@whistle.com Subject: Re: cvs commit: src/sys/netinet in.h ip_fw.h ip_input.c ip_output.c In-reply-to: Your message of "Thu, 22 Aug 1996 14:15:14 PDT." <321CCDE2.794BDF32@whistle.com> Date: Thu, 22 Aug 1996 14:22:16 -0700 From: Paul Traina Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just on the subject of NAT in general, I would strongly suggest anyone considering NAT look at the Linux code. It's not pretty, but one interface that is *critical* is the "nat exceptions" code. They've done a really good job on that bit of work. By NAT exceptions, I mean that there is actual code that sniffs datastreams and looks for things like FTP port numbers and irc DCC's and RealAudio stream IDs, etc. Paul