From owner-freebsd-current Thu Aug 14 12:48:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA08570 for current-outgoing; Thu, 14 Aug 1997 12:48:01 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08561 for ; Thu, 14 Aug 1997 12:47:51 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id PAA15776; Thu, 14 Aug 1997 15:46:45 -0400 (EDT) Date: Thu, 14 Aug 1997 15:46:45 -0400 (EDT) From: Charles Henrich Message-Id: <199708141946.PAA15776@crh.cl.msu.edu> To: jkh@time.cdrom.com, freebsd-current@freebsd.org Subject: Re: Well, I guess it's about time I mentioned this little problem... Newsgroups: lists.freebsd.current References: <5svn1t$qq6$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.current you write: >Any ideas on what I should try here to further debug this oddness? I had a similar problem with SMC cards and some ancient IBM router equipment, setting the MTU to just under 1500 (1450/1480ish) solved the problem. My guess was that the internal buffers in the IBM were broken by being 1500 instead of (1524?) for ethernet packets.. Perhaps it is FreeBSD that is broken? This first showed up when we moved from 2.1 to 2.1.7. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich