Date: Tue, 4 Jan 2005 06:30:26 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Gerrit =?iso-8859-1?Q?K=FChn?= <gerrit@pmp.uni-hannover.de> Cc: freebsd-stable@freebsd.org Subject: Re: Strange networking problems after update 5.2.1->5.3 Message-ID: <20050103193026.GB34222@cirb503493.alcatel.com.au> In-Reply-To: <20050103155826.0fed63ea@arc.pmp.uni-hannover.de> References: <20050103101654.GA51270@pmp.uni-hannover.de> <Pine.NEB.3.96L.1050103131332.46177F-100000@fledge.watson.org> <20050103155826.0fed63ea@arc.pmp.uni-hannover.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2005-Jan-03 15:58:26 +0100, Gerrit Kühn wrote: >ed0: flags=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050103193026.GB34222>