From owner-freebsd-hackers Thu Feb 28 21:57:11 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id 1A88C37B405 for ; Thu, 28 Feb 2002 21:57:07 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g215v2s42804; Thu, 28 Feb 2002 21:57:02 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id VAA1802420; Thu, 28 Feb 2002 21:57:02 -0800 (PST) Message-Id: <200203010557.VAA1802420@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Bob Bishop Cc: Doug Ambrisko , hackers@FreeBSD.ORG Subject: Re: Multicast problem with sis interface? In-Reply-To: Message from Bob Bishop of "Fri, 22 Feb 2002 17:05:41 GMT." <4.3.2.7.2.20020222165515.00c14850@gid.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Feb 2002 21:57:02 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > At 13:10 19/02/02 -0800, Doug Ambrisko wrote: > >Bob Bishop writes: > >| No dice with last night's -STABLE. And it's definitely the interface, I've > >| tried a variety and netatalk works with everything (including the dreaded > >| Via Rhine) except for the onboard sis0. > >| > >| I suppose it's time for some comparative tcpdumping... > > > >Pity that would have been an easy fix. Doing tcpdump should help. > >I like Ethereal so I can drill down a little easier. > > This is what tcpdump (on a disinterested machine) sees: > > sis - fails: > > 20:53:43.423585 255.0.158.nis > 0.0.nis: nbp-lkup 1: "=:=@*" > [addr=255.0.158.128] > aaaa 0308 0007 809b 001a 8369 0000 ff00 > ff9e 0202 0221 01ff 009e 8000 013d 013d > 012a ffff ffff ffff ffff ffff ffff > > vr - works: > > 20:54:55.022827 255.0.158.nis > 0.0.nis: nbp-lkup 1: "=:=@*" > [addr=255.0.158.128] > aaaa 0308 0007 809b 001a 8369 0000 ff00 > ff9e 0202 0221 01ff 009e 8000 013d 013d > 012a 0050 baec bd66 00ff 009e 0000 > > Those trailing 1's look suspicious to me. The NBP lookup packet is only 48 > bytes, so needs padding to the ethernet minimum 60 on the wire. I suspect > this isn't happening on the sis. The packets are otherwise well-formed (and > the ethernet headers (not shown above) are correct). No need. The problem seems to be that at least the National Semi version of the chip does have "Auto Padding" which pads runt packets out to the necessary 60 bytes for Ethernet but that the padding is 1s and not 0s. I seem to remember that according to the Ethernet spec the pad bytes should be 0 but don't quote me. I figured that Auto Padding was not on, but actually it is by default in the driver. You can easily reproduce this bug by doing a ping -s 1 224.0.0.1 on the machine with the sis device. To fix this someone would have to modify sis_encap to pad to the minimum 60 bytes by hand. I'll take a crack at that now. 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