From owner-freebsd-net@FreeBSD.ORG Sat May 3 10:38:58 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7FE037B401 for ; Sat, 3 May 2003 10:38:58 -0700 (PDT) Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8164043FB1 for ; Sat, 3 May 2003 10:38:57 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by wall.polstra.com (8.12.3p2/8.12.3) with ESMTP id h43Hcrdt022827 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 3 May 2003 10:38:53 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.12.6/8.12.6/Submit) id h43HcrIn040717; Sat, 3 May 2003 10:38:53 -0700 (PDT) (envelope-from jdp) Date: Sat, 3 May 2003 10:38:53 -0700 (PDT) Message-Id: <200305031738.h43HcrIn040717@strings.polstra.com> To: net@freebsd.org From: John Polstra In-Reply-To: <3EB3404E.5030103@chikage.wsyntax.com> References: <3EB3404E.5030103@chikage.wsyntax.com> Organization: Polstra & Co., Seattle, WA cc: raymond@chikage.wsyntax.com Subject: Re: IPv6 Neighbor Discovery Problem with dc(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 17:38:59 -0000 In article <3EB3404E.5030103@chikage.wsyntax.com>, Raymond Jimenez wrote: > On my network, several machines are having trouble recognizing an icmp6 > neighbor solicitation. This only happens to me when I use the dc driver, > in combination with the ADMTek AN985 10/100BaseTX chipset. The machines > are running a combination of 4.7 and -CURRENT. The network topology > consists of 3 switches, 2 of Linksys make, and 1 of Gigafast make. The > computers will not recognize each other even when on the same switch. > Tcpdump on the sender of the packet shows that the other interface > (should be) reciving the packets, but is sending out no reply. When two > computers are using any other driver than dc(4), they can ping each > other. However, when tcpdump is done on the system with dc, the other > can ping it and send data packets back and forth. It continues working > after tcpdump is stopped. I've searched, and found nothing. > Is there something I should check? This sounds a lot like a multicast-related bug that may have been fixed just two days ago in -current. Here is the log message from "src/sys/pci/if_dc.c": revision 1.106 date: 2003/05/01 09:31:01; author: mbr; state: Exp; lines: +5 -1 Use only a 64bit hash filter table for ADM-Centaur cards like the Accton EN2242 and the ADMtek AN985 cards. PR: 32699 Submitted by: Jean-Luc Richier Reviewed by: phk MFC after: 2 weeks John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Two buttocks cannot avoid friction." -- Malawi saying