Date: Tue, 4 Aug 1998 22:08:31 +0200 (CEST) From: Stefan Bethke <stb@hanse.de> To: Julian Elischer <julian@whistle.com> Cc: Parag Patel <parag@cgt.com>, current@FreeBSD.ORG Subject: Re: Netatalk name-registering problem with -current Message-ID: <Pine.BSF.3.96.980803224405.10187B-100000@transit.hanse.de> In-Reply-To: <Pine.BSF.3.95.980801125913.15201A-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 1 Aug 1998, Julian Elischer wrote: > yes there is a problem with -current and netatalk name registration. > > it's on my list of things to look at.. > there are two suspicious areas.. I've delved a bit into this and think I've found the problem. In net/ether_output, around line 365, if_simloop() is called with a fixed LLC header length of ETHER_HDR_LEN, instead of whatever length the header has (in case of a SNAP frame [Phase 2], its a LLC header). Currently testing, patch forthcoming... Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg <stefan.bethke@hanse.de> Hamburg, Germany <stb@freebsd.org> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980803224405.10187B-100000>