From owner-freebsd-hackers Thu Mar 6 14:00:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA14384 for hackers-outgoing; Thu, 6 Mar 1997 14:00:35 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14374 for ; Thu, 6 Mar 1997 14:00:28 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id JAA02900; Fri, 7 Mar 1997 09:17:09 +1100 (EST) Date: Fri, 7 Mar 1997 09:17:08 +1100 (EST) From: "Daniel O'Callaghan" To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: Weirdie with SLIP line seen here too... In-Reply-To: <2805.857653321@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 6 Mar 1997, Jordan K. Hubbard wrote: > Strange, now I'm seeing that magic "bit pattern-o-death" that > guarantees that the download of a given file over a slip line will > always hang in a given place. See if any of you fellow sufferers can > download the following file: > > ftp://freefall.freebsd.org/pub/jkh/badbits > > If not, we may be onto something which could enable more reasonable > failure analysis to take place. This is getting really weird. There seems to be more in it than just the file itself. ether/E1 CSLIP ether world---------skylark----------panda--------test2 MTU1500 MTU552 LAN panda has no problems, even with rfc1323=1 test2 cannot fetch if rfc1323=1 test2 cannot fetch if MTU > 552 test2 can fetch if ( MTU == 552 && rfc1323 == 0 ) I'll do some tcpdumping and send the trace. I have a feeling that the DF flag is the problem. Danny