From owner-freebsd-net Sun Feb 20 9:45:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.snickers.org (mail.snickers.org [216.126.90.4]) by hub.freebsd.org (Postfix) with ESMTP id 399C137BEC5 for ; Sun, 20 Feb 2000 09:45:50 -0800 (PST) (envelope-from josh@snickers.org) Received: by mail.snickers.org (Postfix, from userid 1037) id 9F3993D84; Sun, 20 Feb 2000 12:45:44 -0500 (EST) Date: Sun, 20 Feb 2000 12:45:44 -0500 From: Josh Tiefenbach To: Corigan Cc: Dermot McNally , freebsd-net@freebsd.org Subject: Re: Solved: NAT with PPPoE problems (was: NAT issues with ppp) Message-ID: <20000220124544.A11945@snickers.org> References: <4.2.0.58.20000215233615.02334c30@tim> <4.2.0.58.20000220172816.00a38778@tim> <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com> Organization: Hah Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've never really had a problem with the -nat command of ppp and my PPPoE > connection except that the http pages will not load up. I noticed this problem as well (at least with machines behind the NAT gateway). The problem would be that you'd get pretty much the headers and the first couple of lines from the page before the connection would hang. I personally suspected that there was some evil interaction between my NAT gateway and the transparent proxying that my provider does. Setting up squid on the gateway solved the problem. Just as a data point, the same behavior is evidenced in both ppp -nat and using ipnat (part of IPFilter v3.3.8 in -current). And just for the record, I tried reducing the MTU on the machine behind the gateway, and things 'worked'. Interesting. josh -- Give me rampant intellectualism as a coping strategy! -- Chuck Palahniuk in Invisible Monsters To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message