From owner-freebsd-stable@FreeBSD.ORG Mon Jan 3 19:30:31 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 242FB16A4CE for ; Mon, 3 Jan 2005 19:30:31 +0000 (GMT) Received: from mail18.syd.optusnet.com.au (mail18.syd.optusnet.com.au [211.29.132.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71F4A43D49 for ; Mon, 3 Jan 2005 19:30:30 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j03JUS12026891 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 4 Jan 2005 06:30:29 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j03JURxP036421; Tue, 4 Jan 2005 06:30:27 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j03JUQiS036420; Tue, 4 Jan 2005 06:30:27 +1100 (EST) (envelope-from pjeremy) Date: Tue, 4 Jan 2005 06:30:26 +1100 From: Peter Jeremy To: Gerrit =?iso-8859-1?Q?K=FChn?= Message-ID: <20050103193026.GB34222@cirb503493.alcatel.com.au> References: <20050103101654.GA51270@pmp.uni-hannover.de> <20050103155826.0fed63ea@arc.pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20050103155826.0fed63ea@arc.pmp.uni-hannover.de> User-Agent: Mutt/1.4.2i 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: Mon, 03 Jan 2005 19:30:31 -0000 On Mon, 2005-Jan-03 15:58:26 +0100, Gerrit Kühn wrote: >ed0: flags=108843 mtu 1500 > inet 130.75.117.37 netmask 0xffff0000 broadcast 130.75.255.255 > ether 01:d4:ff:03:00:20 That's a multicast MAC address (the LSB of the first byte is 1). More intelligent NICs will have an internal list of multicast MAC addresses that they have been programmed to respond to and will ignore all other multicast addresses (for dumber NICs, this checking should be in the driver). This would explain the peculiar behaviour you are seeing. Firstly, I presume you're not attempting to change the MAC address. Secondly, the MAC address should be reported as part of the ed0 probe message - can you have a look back through your messages file and report the ed0 probe messages for both 5.2.1 and 5.3. -- Peter Jeremy