From owner-freebsd-net Sun Feb 20 9:23:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (Postfix) with ESMTP id AAC8A37BEB0 for ; Sun, 20 Feb 2000 09:23:22 -0800 (PST) (envelope-from dermot@mcnally.de) Received: from TIGGER (p3E9ECFC2.dip.t-dialin.net [62.158.207.194]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id JAA00121; Sun, 20 Feb 2000 09:22:16 -0800 (PST) Message-Id: <4.2.0.58.20000220182204.00a4f7d0@tim> X-Sender: dermot@tim X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 20 Feb 2000 18:25:18 +0100 To: "Corigan" From: Dermot McNally Subject: Re: Solved: NAT with PPPoE problems (was: NAT issues with ppp) Cc: In-Reply-To: <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com> References: <4.2.0.58.20000215233615.02334c30@tim> <4.2.0.58.20000220172816.00a38778@tim> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:55 20.02.2000 -0500, Corigan wrote: >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. Well, this _is_ a problem, no? The whole point of NAT is that it's supposed to allow arbitrary connections through your gateway, and once HTTP fails, you can't tell what else might also go wrong. For me, HTTP was the most important and most noticeable failure, but there were others. > I just assume this >is cause of apache and setup a little proxy. No, simply having Apache installed on your gateway can't cause this problem. But as you say, a proxy will go some way to fixing it... > If it isn't, I wonder what is >up with that. Glas to see you got it working friend. It looks like your problem is the same as mine. Try reducing the MTU on all of your local network interfaces. I used a setting of 1400 and everything now works the way I expect. Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message