Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12816 comp.os.386bsd.bugs:2462 comp.os.386bsd.development:2521 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!gatech!swrinde!cs.utexas.edu!utnut!torn!uunet.ca!uunet.ca!fw.novatel.ca!sidney.novatel.ca!hpeyerl From: hpeyerl@sidney.novatel.ca (Herb Peyerl) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs,comp.os.386bsd.development Subject: Re: FreeBSD IP problem? Followup-To: comp.os.386bsd.questions,comp.os.386bsd.bugs,comp.os.386bsd.development Date: 1 Sep 1994 14:23:54 GMT Organization: NovAtel Communications Ltd. Lines: 20 Message-ID: <344o5q$dmq@fw.novatel.ca> References: <33tee7INN7vr@scarecrow.mke.ab.com> NNTP-Posting-Host: sidney.novatel.ca X-Newsreader: TIN [version 1.2 PL1] Thad Phetteplace x4461 (tdphette@mke.ab.com) wrote: : The problem seems to occur when there is garbage data in the ethernet : frame following the end of the IP packet. Our testing shows that this More details. Where does this garbage occur? How long is it? Is it merely just an alignment problem? : the kernel code") Should I be focusing on the driver for my specific : network card? (3c509) What part of the kernel source code should I : be looking at? It sounds to me as though; if anywhere; you would want to look higher than the device-driver layer. The device driver is only responsible for pulling an entire frame off the cable and passing it upstairs or taking what has been dumped in its lap and dumping it on the wire... -- hpeyerl@novatel.ca | NovAtel Communications Ltd. hpeyerl@fsa.ca | <nothing I say matters anyway> "A sucking chest wound is nature's way of telling you to slow down."