From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philip Craig Subject: Re: DNAT pptp to windows machine Date: Wed, 03 Aug 2005 16:25:02 +1000 Message-ID: <42F0633E.4020000@snapgear.com> References: <04a101c597aa$2db2bc50$1500a8c0@domain.internationalauto.com> <01d001c597f2$246fe580$0100a8c0@newlife> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <01d001c597f2$246fe580$0100a8c0@newlife> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii" To: netfilter@lists.netfilter.org Ming-Ching Tiew wrote: > As far as I know, PPTP connection tracking is for the PPTP client going > through firewall, ie pptp masquerade. It is not needed for DNAT of PPTP > into a pptp server. The PPTP connection tracking works for both clients and servers, since after all, you need one of each to make a PPTP connection. While you can get by without it for DNAT to a server, the PPTP connection tracking allows you to automatically NAT the related GRE connections, and you can use a conntrack state match to only allow related GRE packets through the firewall.