i386/144492: The fxp driver does not handle Frame Check Sequence (CRC) errors correctly.

[Rainer Bredehorn]

>Number:         144492
>Category:       i386
>Synopsis:       The fxp driver does not handle Frame Check Sequence (CRC) errors correctly.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-i386
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 05 13:40:01 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     Rainer Bredehorn
>Release:        FreeBSD 7.1
>Organization:
>Environment:
>Description:
If a Frame Check Sequence (FCS) of a packet is wrong you can see this packet with a packet sniffer (wireshark/tcpdump) via the BPF hook in the ether_input() function.
Other network driver discard the frame.

File: sys/dev/fxp/if_fxp.c
Function: fxp_intr_body

The error handling after checking the status flag FXP_RFA_STATUS_CRC seems to be wrong. 
>How-To-Repeat:
Connect the FreeBSD 7.1 machine to a ethernet hub. Generate traffic so that the hub shows collisions.

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: