From owner-freebsd-bugs@FreeBSD.ORG Mon Jun 23 16:00:36 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E750A37B401 for ; Mon, 23 Jun 2003 16:00:36 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DACC943F3F for ; Mon, 23 Jun 2003 16:00:35 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h5NN0ZUp054409 for ; Mon, 23 Jun 2003 16:00:35 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5NN0ZPE054408; Mon, 23 Jun 2003 16:00:35 -0700 (PDT) Resent-Date: Mon, 23 Jun 2003 16:00:35 -0700 (PDT) Resent-Message-Id: <200306232300.h5NN0ZPE054408@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, iasenkk@hotmail.com Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5166437B401 for ; Mon, 23 Jun 2003 15:52:59 -0700 (PDT) Received: from www.otel.net (ScooteR.OTEL.net [212.36.8.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1291843F3F for ; Mon, 23 Jun 2003 15:52:57 -0700 (PDT) (envelope-from tbyte@www.otel.net) Received: from www.otel.net (localhost.otel.net [127.0.0.1]) by www.otel.net (8.12.6/8.12.6) with ESMTP id h5NMqrrT056257 for ; Tue, 24 Jun 2003 01:52:53 +0300 (EEST) (envelope-from tbyte@www.otel.net) Received: (from tbyte@localhost) by www.otel.net (8.12.6/8.12.6/Submit) id h5NMqrtp056256; Tue, 24 Jun 2003 01:52:53 +0300 (EEST) Message-Id: <200306232252.h5NMqrtp056256@www.otel.net> Date: Tue, 24 Jun 2003 01:52:53 +0300 (EEST) From: iasenkk@hotmail.com To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: kern/53656: Problem with if_dc and Davicom DM9102AF X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: iasenkk@hotmail.com List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 23:00:37 -0000 >Number: 53656 >Category: kern >Synopsis: Problem with if_dc and Davicom DM9102AF >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 23 16:00:35 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Iasen Kostoff >Release: FreeBSD 4.8-STABLE i386 >Organization: OTEL.net >Environment: System: FreeBSD TiTaN.OTEL.net 4.8-STABLE FreeBSD 4.8-STABLE #1: Tue Jun 24 00:13:04 EEST 2003 root@TiTaN.OTEL.net:/usr/src/sys/compile/TITAN i386 >Description: There is a problem with dc(4) driver working with DM9102AF Driver detects card ad DM9102A it detects link but when you try to ping another host it can't resolve arp address. Interesting is that you can ping host A (dc(4) host) from host B (whatever card it has) but that is not true for host A pinging B even if host A know arp address of host B (the ping form host B teaches A what is his lladdr). This problem as I saw is not just on particular machines. I saw reports of the same bug in some mailing list. I even try the same with other machine and other card of same type and the problem still presist. Some say that it happen to work with old 4.4 drivers on 4.7 but it is not true on 4.8-STABLE. >How-To-Repeat: Buy CNet Pro200 LAN Card :) >Fix: >Release-Note: >Audit-Trail: >Unformatted: