From owner-freebsd-bugs Thu Jun 4 01:28:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26965 for freebsd-bugs-outgoing; Thu, 4 Jun 1998 01:28:33 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26941 for ; Thu, 4 Jun 1998 01:28:29 -0700 (PDT) (envelope-from hans@news.IAEhv.nl) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.8.8/1.63) with IAEhv.nl; pid 7062 on Thu, 4 Jun 1998 08:28:27 GMT; id IAA07062 efrom: hans; eto: freebsd-bugs@freebsd.org Received: by truk.brandinnovators.com (8.8.7/BI96070101) for id JAA10331; Thu, 4 Jun 1998 09:58:21 +0200 (CEST) Message-Id: <199806040758.JAA10331@truk.brandinnovators.com> From: hans@brandinnovators.com (Hans Zuidam) Subject: if_ed/tcpdump problem To: freebsd-bugs@FreeBSD.ORG Date: Thu, 4 Jun 1998 09:58:20 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have FreeBSD 2.2.5-RELEASE running with two NE2000 clones (if_ed) connecting to two different networks. This has worked quite well over the past year. >From the logs and ifconfig: May 25 17:05:44 truk /kernel: ed0 at 0x300-0x31f irq 5 on isa May 25 17:05:44 truk /kernel: ed0: address 00:40:95:50:28:b5, type NE2000 (16 bit) May 25 17:05:44 truk /kernel: ed1 at 0x320-0x33f irq 10 on isa May 25 17:05:44 truk /kernel: ed1: address 00:40:f6:14:bc:e3, type NE2000 (16 bit) ed0: flags=8843 mtu 1500 inet 192.9.200.10 netmask 0xffffff00 broadcast 192.9.200.255 ether 00:40:95:50:28:b5 ed1: flags=8843 mtu 1500 inet 192.9.201.31 netmask 0xffffff00 broadcast 192.9.201.255 ether 00:40:f6:14:bc:e3 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 Now a strange problem has surface with one of the interfaces (ed1). When connecting to a host using TCP everything works well, when ping-ing everything works well, but when connecting using a UDP based application I get a lot of "NIC memory corrupt messages": Jun 4 08:54:54 truk /kernel: ed1: NIC memory corrupt - invalid packet length 4299 Jun 4 08:54:55 truk /kernel: ed1: NIC memory corrupt - invalid packet length 8439 Jun 4 08:54:55 truk /kernel: ed1: NIC memory corrupt - invalid packet length 8434 The strange thing is that they are not generated if I do not use tcpdump on the interface. If I use tcpdump, then I see a lot of: 09:27:41.473402 Broadcast Broadcast ffff 1185: ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff The other host reports lots of late collisions (collisions after 64 byte times into the transmission.) Any ideas what might be wrong? Thanks in advance, Hans -- H. Zuidam E-Mail: hans@brandinnovators.com Brand Innovators B.V. P-Mail: P.O. Box 1377 de Pinckart 54 5602 BJ Eindhoven, The Netherlands 5674 CC Nuenen Tel. +31 40 2631134, Fax. +31 40 2831138 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message