Date: Fri, 01 Mar 2002 09:49:50 -0800 From: "George V. Neville-Neil" <gnn@neville-neil.com> To: Luigi Rizzo <rizzo@icir.org> Cc: Bob Bishop <rb@gid.co.uk>, Doug Ambrisko <ambrisko@ambrisko.com>, hackers@FreeBSD.ORG Subject: Re: Multicast problem with sis interface? Message-ID: <200203011749.JAA1797377@meer.meer.net> In-Reply-To: Message from Luigi Rizzo <rizzo@icir.org> of "Fri, 01 Mar 2002 03:56:23 PST." <20020301035623.A32974@iguana.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I find this hard to believe. The "sis" driver does the padding > itself, using ones for the padding. I have verified this locally. > And a switch which receives a short packet (runt packet) is > not supposed to pass it through. I have verified this as well, and did before I hacked that patch together. > > ed, vr, rl > > ok, these three drivers behave as follows: > > "ed" pads with whatever is left in the transmit buffer from > earlier transmissions; > "vr" pads with whatever is available in the mbuf after the actual data; > "rl" pads with zeroes (in the driver) > and of course > "sis" pads in hardware (with ones) > I'm downloading the 802.3 spec now. Just to be sure. Of course I have no problem letting the driver stand as is if it's "right" but my memory, which I'm checking via the spec, is that short packets are to be padded with 0s. More when the darned things are done. BTW I've no attachment to putting this change in, I decided to check/fix this as a way of testing my new development environment. We can always close the PR, which is kern/35442. Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203011749.JAA1797377>