Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!demon!ronald From: ronald@demon.co.uk (Ronald Khoo) Subject: Re: NetBSD-0.9 ne0: errors Message-ID: <CtK0z1.Ltp@demon.co.uk> Organization: Demon Internet Limited References: <310qnd$sfk@sun.cais.com> <MYCROFT.94Jul26024509@duality.gnu.ai.mit.edu> Date: Tue, 26 Jul 1994 15:42:36 GMT Lines: 21 In article <MYCROFT.94Jul26024509@duality.gnu.ai.mit.edu>, Charles M. Hannum <mycroft@duality.gnu.ai.mit.edu> wrote: > >In article <310qnd$sfk@sun.cais.com> martinj@cais.cais.com (James >Martin) writes: > > also anything I ping from the boxes comes back with lots of DUP > packets. > >The `ne' driver in 0.9 was not very good, to put it nicely. The >upcoming 1.0 release has a much more reliable driver in it. If you need to do something as a stopgap measure, there's one bug in if_ne.c that's easy to cure that causes the DUPs. Where the cmd gets stored then replaced (a few places) you must use (cmd & ~ DSCM_TRANS) instead of just cmd otherwise the packet you're currently transmitting may get transmitted *again* and *again* and *again* causing the DUPs. The new if_ed driver in NetBSD-1.0 alpha does not have this kind of mess. Upgrade if you can, as soon as you can.