Bug 21176

Summary: Malformed packets on fxp driver
Product: Base System Reporter: venglin <venglin>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.1-STABLE   
Hardware: Any   
OS: Any   

Description venglin 2000-09-10 22:50:01 UTC
Packets coming from fxp1 interface are malformed:

23:22:13.931265 0:90:27:a3:f1:0 ff:ff:ff:ff:ff:ff 0800 98: 10.10.11.1 > 10.10.11.255: icmp: echo request
                         4500 0054 7470 0000 ff01 1c25 0a0a 0b01
                         0a0a 0bff 0800 6e7b 7616 3500 85fb bb39
                         a435 0e00 0809 0a0b 0c0d 0e0f 1011 1213
                         1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
                         2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
                         3435
23:22:14.941266 ff:ff:ff:ff:0:90 2:0:0:0:ff:ff 27a3 102: 
                         f100 0800 4500 0054 747f 0000 ff01 1c16
                         0a0a 0b01 0a0a 0bff 0800 5654 7616 3600
                         86fb bb39 ba5c 0e00 0809 0a0b 0c0d 0e0f
                         1011 1213 1415 1617 1819 1a1b 1c1d 1e1f
                         2021 2223 2425 2627 2829 2a2b 2c2d 2e2f
                         3031

Received packet is padded with 4 bytes (0xff) on the beginning. It is not
a hardware failure. Everything worked on 5.0-CURRENT.

Packets from fxp0 are good.

Fix: 

Unknown.
How-To-Repeat: 
Send some packets to broadcast address on second fxp NIC. Catch
responses with tcpdump -x.
Comment 1 Przemyslaw Frasunek 2000-09-11 14:52:15 UTC
On Sun, Sep 10, 2000 at 09:42:07PM -0000, venglin@ismedia.pl wrote:
> Received packet is padded with 4 bytes (0xff) on the beginning. It is not
> a hardware failure. Everything worked on 5.0-CURRENT.

Please close this PR. Problem recognized as hardware failure.

-- 
* Fido: 2:480/124 ** WWW: http://www.freebsd.lublin.pl ** NIC-HDL: PMF9-RIPE *
* Inet: venglin@freebsd.lublin.pl ** PGP: D48684904685DF43  EA93AFA13BE170BF *
Comment 2 dwmalone freebsd_committer freebsd_triage 2000-09-11 15:25:13 UTC
State Changed
From-To: open->closed

Problem due to hardware fault according to submitter.