From owner-freebsd-net Sat Mar 4 16:27:21 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 908BE37B93D; Sat, 4 Mar 2000 16:27:18 -0800 (PST) (envelope-from dermot@mcnally.de) Received: from TIGGER (p3E9ECFDE.dip.t-dialin.net [62.158.207.222]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA01905; Sat, 4 Mar 2000 16:26:35 -0800 (PST) Message-Id: <4.2.0.58.20000305012120.02aa77e0@tim> X-Sender: dermot@tim X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 05 Mar 2000 01:29:54 +0100 To: Brian Somers , Dermot McNally From: Dermot McNally Subject: Re: NAT issues with ppp - a fix Cc: Brian Somers , freebsd-net@FreeBSD.org, peter@FreeBSD.org, jkh@FreeBSD.org, joe@FreeBSD.org In-Reply-To: <200003040218.CAA02929@hak.lan.Awfulhak.org> References: 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 02:18 04.03.2000 +0000, Brian Somers wrote: >Hi, > >Because of a recent change in the way I connect to the net >(PPPoUDPoPPPoISDN), I'm now seeing this problem ! > >Can you try the attached patch ? I believe this fixes the problem ! Bad news on my side - it doesn't appear to have helped. My test case: Before applying the patch, I cvsupped to today's current and rebuilt the world. Then I set the gateway box and a FreeBSD alpha box on my internal network back to an MTU of 1500. I connected to confirm that the problem was still there (it was). Then I applied the patch, rebuilt and installed ppp. Same test. Same problem - well, same symptoms anyway. My two tests were, using Lynx to connect to effectively any WWW site and using fetch to download a biggish file. Fetch determines the file size (which I don't recall it managing to do before), but doesn't actually get any further with the download. Lynx manages to look up the site to which I try to connect, but then hangs at the "waiting for response" stage. I can packet sniff this if you think it will help - my setup is slightly different to yours: PPPoE via a DSL "modem". Slightly related: Assuming you do manage to fix things so that fragmented packets are properly aliased (and it's probably a good thing, overall), a convenient side effect of the current problem is that we notice that fragmentation is occurring and drop our MTUs to avoid it. Since fragmentation is worth avoiding anyway, is there value in having PPP log a warning if it is seen to occur? Cheers, Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message