Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!ucbvax!mtxinu!rtech!wrs!hwajin From: hwajin@ganges.wrs.com (Hwa Jin Bae) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: pc/ip NETWATCH Message-ID: Date: 5 Feb 90 00:37:33 GMT References: <9002021451.AA16006@vax.ftp.com> Sender: news@wrs.wrs.com Organization: Wind River Systems, Emeryville, CA Lines: 19 In-reply-to: jbvb@VAX.FTP.COM's message of 2 Feb 90 14:51:01 GMT In article <9002021451.AA16006@vax.ftp.com> jbvb@VAX.FTP.COM (James Van Bokkelen) writes: > DRIBBLE is a 3Com-ism (I think) for packets that didn't end on an even > byte boundary. In LANWatch, at least, the only interface that can > generate DRIBBLE errors is the 3C500, where I believe It is a synonym > for "alignment errors". Other interfaces call the same condition an > ALIGN error. Dribble error is part of the ethernet terminology and some ethernet chips support the generation/detection of this error (e.g. LANCE) so I don't think this is unique to the 3Com or more specifically the boards they manufacture. hwajin -- Hwa Jin Bae, Wind River Systems, Emeryville CA hwajin@wrs.com (uunet!wrs!hwajin) -- Hwa Jin Bae, Wind River Systems, Emeryville CA hwajin@wrs.com (uunet!wrs!hwajin)