NetBSD Problem Report #25096

Received: (qmail 25189 invoked by uid 605); 7 Apr 2004 19:03:27 -0000
Message-Id: <20040407190323.D6B8B739A9B@emmas.aprisoft.de>
Date: Wed,  7 Apr 2004 21:03:23 +0200 (CEST)
From: martin@aprisoft.de
Sender: gnats-bugs-owner@NetBSD.org
Reply-To: martin@aprisoft.de
To: gnats-bugs@gnats.NetBSD.org
Subject: kernels with DIAGNOSTIC can't use rarp to boot with some network drivers
X-Send-Pr-Version: 3.95

>Number:         25096
>Category:       kern
>Synopsis:       kernels with options DIAGNOSTIC can't use rarp to boot with some network drivers
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 07 19:04:00 +0000 2004
>Closed-Date:    Wed May 23 06:24:16 +0000 2018
>Last-Modified:  Wed May 23 06:24:16 +0000 2018
>Originator:     Martin Husemann
>Release:        NetBSD 2.0_BETA
>Organization:

>Environment:
System: NetBSD emmas.aprisoft.de 2.0_BETA NetBSD 2.0_BETA (EMMAS) #0: Wed Apr 7 12:44:53 CEST 2004 martin@emmas.aprisoft.de:/usr/src/sys/arch/i386/compile/EMMAS i386
Architecture: sparc
Machine: sparc
>Description:

When netbooting a sparc via the be0 interface. The following section from
sys/dev/sbus/be.c is hit:

#ifdef DIAGNOSTIC         
        if (len < ETHER_MIN_LEN || len > ETHER_MAX_LEN + ETHERCAP_VLAN_MTU) {
                printf("%s: invalid packet size %d; dropping\n",   
                        ifp->if_xname, len);
                ifp->if_ierrors++;
                return;
        }
#endif

and complains about 60 byte "rarp reply" packets. This looks like FCS not
being counted in len, but supposed to be at the ETHER_MIN_LEN definition.

I did not do a complete audit, but it looks like this problem would exist
for several network drivers.

>How-To-Repeat:
Code inspection.

>Fix:
Decide, if FCS is included in ETHER_MIN_LEN and make it consistently so.
>Release-Note:
>Audit-Trail:

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@gnats.NetBSD.org
Cc:  
Subject: Re: kern/25096: kernels with DIAGNOSTIC can't use rarp to boot with some network drivers
Date: Thu, 8 Apr 2004 02:22:59 +0200

 Never do math when you are tired and realy need to go home ...

 Ignore the FCS theory - just tell me, what is wrong and how to fix it.

 Martin
State-Changed-From-To: open->closed
State-Changed-By: martin@NetBSD.org
State-Changed-When: Wed, 23 May 2018 06:24:16 +0000
State-Changed-Why:
This probably was caused by a padding bug in the ethernet driver of the
machine running arpd - unfortunately the details are unknown and we
can't know for sure which driver that was and wether it was fixed
since then.


>Unformatted:

Home	PR Database Search