From owner-freebsd-hackers Thu Sep 19 14:40:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA03981 for hackers-outgoing; Thu, 19 Sep 1996 14:40:28 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA03956 for ; Thu, 19 Sep 1996 14:40:25 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA01485; Thu, 19 Sep 1996 14:38:51 -0700 From: Terry Lambert Message-Id: <199609192138.OAA01485@phaeton.artisoft.com> Subject: Re: Giant Sized Ethernet Packets To: matt@lkg.dec.com (Matt Thomas) Date: Thu, 19 Sep 1996 14:38:51 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@freebsd.org In-Reply-To: <199609191638.QAA26304@whydos.lkg.dec.com> from "Matt Thomas" at Sep 19, 96 04:38:09 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I would find this suprising, since it would imply that DEC's cards can't > > run DECNet (which has a nasty habit of shoving huge frames around). > > That is *complete* and *utter* bullsh*t. DECnet uses standard size > Ethernet frames. Always has, always will. We had problems with DECNet Phase IV protocols, specificall MOP, specifically MOP-MOM responses generating large frames at Weber State University during the download of DECServer 200's from VMS 4.x systems. This may have been an implementation error or something else; nevertheless, we did have problems, and that is what the DEC field support rep claimed when he suggested we replace some of our non-DEC hardware. > Again, no DEC developed protocol uses over-sized Ethernet frames. What's "oversized"? How many bytes, exactly? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.