Date: Sun, 20 Feb 2000 12:45:44 -0500 From: Josh Tiefenbach <josh@zipperup.org> To: Corigan <corigan@mindspring.com> Cc: Dermot McNally <dermot@mcnally.de>, freebsd-net@freebsd.org Subject: Re: Solved: NAT with PPPoE problems (was: NAT issues with ppp) Message-ID: <20000220124544.A11945@snickers.org> In-Reply-To: <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com> References: <Message <dermot@mcnally.de><4.2.0.58.20000215233615.02334c30@tim> <4.2.0.58.20000220172816.00a38778@tim> <000f01bf7bc3$3a8cac00$0100a8c0@zeist.sweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000220124544.A11945>