From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 03:05:09 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7ACA37B401 for ; Fri, 18 Jul 2003 03:05:09 -0700 (PDT) Received: from exchange.wan.no (exchange.wan.no [80.86.128.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9750243F93 for ; Fri, 18 Jul 2003 03:05:08 -0700 (PDT) (envelope-from sten.daniel.sorsdal@wan.no) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Fri, 18 Jul 2003 12:03:43 +0200 Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F1F3DF4@exchange.wanglobal.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NAT and PPTP Thread-Index: AcNMmo3QJfAOFMqlRG2kR9U0vBGG/wAeQXUA From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= To: "Brett Glass" , Subject: RE: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 10:05:10 -0000 =20 > FreeBSD makes a very good NAT router... for most applications. > But a client of mine is having terrible trouble with it when > trying to use NAT with one particular protocol: PPTP. >=20 > Here's what's going on. A client has a FreeBSD box that's serving as a > NAT router. He has one public IP, and lots of PCs behind the router on > unregistered IPs. This works fine when they're doing=20 > browsing, etc., but > fails horribly when users try to use PPTP to tunnel out into=20 > another LAN > across the Internet. >=20 natd handles pptp. we have multiple clients who are NATed and they = connect to different pptp gateways (occasionally the same too). if you are running a poptop pptp server and you want multiple clients=20 connecting to this one pptp server; make sure you get the GRE ID update (poptop always sets the id to 0 - messes up two connections). make sure you divert gre packets on their way out as well. - sten