From owner-freebsd-questions Thu Mar 15 2:20:28 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id E785637B719; Thu, 15 Mar 2001 02:20:21 -0800 (PST) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f2FAAvx03944; Thu, 15 Mar 2001 02:10:57 -0800 (PST) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Robert Clark" Cc: "Bob Van Valzah" , "pW" , , Subject: RE: Racoon Problem & Cisco Tunnel Date: Thu, 15 Mar 2001 02:10:56 -0800 Message-ID: <006b01c0ad38$39eed0a0$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: <20010313104927.A59404@darkstar.gte.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Robert Clark > >Ted, do you know of any online guidelines to wrting protocols >that function well with NAT? > The rule of thumb is don't embed port information in the data payload. But here's some references: K. Egevang, P. Francis, "The IP Network Address Translator(NAT)", RFC 1631, May 1994. T. Hain, "Architectural Implications of NAT", Internet Draft,July 1998. Matt Holdrege, Pyda Srisuresh, "IP Network Address Translator(NAT) Protocol Issues", Internet Draft, August 1998. Yakov Rekhter, "Implications of NAT’s on the TCP/IParchitecture", Internet Draft, August 1998. P. Srisuresh, Matt Holdrege, "IP Network Address Translator(NAT) Terminology and Considerations", Internet Draft, July 1998. This list is from a post that Jim Gray made to the Questions list back in October that was very good. > >Or maybe a list of protocols that don't work well with NAT? > This is entirely implementation dependent. For example, Cisco has a list somewhere on their website that shows the ones they do and don't support. I don't know if anyone has made up a list for natd. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message