From owner-freebsd-stable@FreeBSD.ORG Tue Jan 4 09:17:11 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 526EB16A4CE for ; Tue, 4 Jan 2005 09:17:11 +0000 (GMT) Received: from mrelay3.uni-hannover.de (mrelay3.uni-hannover.de [130.75.2.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1552143D48 for ; Tue, 4 Jan 2005 09:17:10 +0000 (GMT) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2])j049H69e001687; Tue, 4 Jan 2005 10:17:06 +0100 (MET) Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 033D775; Tue, 4 Jan 2005 10:17:02 +0100 (CET) Date: Tue, 4 Jan 2005 10:17:01 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Peter Jeremy Message-Id: <20050104101701.3a08b138.gerrit@pmp.uni-hannover.de> In-Reply-To: <20050103193026.GB34222@cirb503493.alcatel.com.au> References: <20050103101654.GA51270@pmp.uni-hannover.de> <20050103155826.0fed63ea@arc.pmp.uni-hannover.de> <20050103193026.GB34222@cirb503493.alcatel.com.au> Organization: Plasmaphysik X-Mailer: Sylpheed version 1.0.0rc (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.2.2 (mrelay3.uni-hannover.de [130.75.2.41]); Tue, 04 Jan 2005 10:17:06 +0100 (MET) X-Scanned-By: MIMEDefang 2.42 cc: freebsd-stable@freebsd.org Subject: Re: Strange networking problems after update 5.2.1->5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 09:17:11 -0000 On Tue, 4 Jan 2005 06:30:26 +1100 Peter Jeremy wrote about Re: Strange networking problems after update 5.2.1->5.3: PJ> >ed0: flags=108843 mtu 1500 PJ> > inet 130.75.117.37 netmask 0xffff0000 broadcast 130.75.255.255 PJ> > ether 01:d4:ff:03:00:20 PJ> That's a multicast MAC address (the LSB of the first byte is 1). More Ok, I didn't know about this. Can you recommend any online resource where those special things are documented? PJ> intelligent NICs will have an internal list of multicast MAC addresses PJ> that they have been programmed to respond to and will ignore all other PJ> multicast addresses (for dumber NICs, this checking should be in the PJ> driver). This would explain the peculiar behaviour you are seeing. For sure. PJ> Firstly, I presume you're not attempting to change the MAC address. Correct, I even don't know how to do this. ;-) PJ> Secondly, the MAC address should be reported as part of the ed0 probe PJ> message - can you have a look back through your messages file and PJ> report the ed0 probe messages for both 5.2.1 and 5.3. Ok, 5.2.1 reported the following Dec 28 10:15:05 lonestar kernel: ed1: at port 0x100-0x11f irq 11 function 0 config 16 on pccard1 Dec 28 10:15:05 lonestar kernel: ed1: address 00:e0:98:a2:a7:33, type Linksys (16 bit) Dec 28 10:15:05 lonestar kernel: miibus0: on ed1 With 5.3 it says Dec 29 15:48:15 lonestar kernel: ed1: at port 0x100-0x11f irq 11 function 0 config 16 on pccard1 Dec 29 15:48:15 lonestar kernel: ed1: [GIANT-LOCKED] Dec 29 15:48:15 lonestar kernel: ed1: Ethernet address: 01:d4:ff:03:00:20 Dec 29 15:48:15 lonestar kernel: ed1: if_start running deferred for Giant Dec 29 15:48:15 lonestar kernel: type NE2000 (16 bit) I admit that I've got no clue where this new MAC is coming from. :) cu Gerrit