Newsgroups: comp.protocols.tcp-ip.ibmpc Path: utzoo!news-server.csri.toronto.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Subject: Re: NE1000 PD problem found, WATCH FOR BAD CARD ADRESSES! Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Date: 18 Mar 91 12:02:25 Message-ID: In-Reply-To: mah@dec1.wu-wien.ac.at's message of 7 Mar 91 18:04:39 GMT References: <1991Mar06.004805.5386@nestroy.wu-wien.ac.at> <1991Mar06.144438.21803@nestroy.wu-wien.ac.at> <1991Mar07.180439.5382@nestroy.wu-wien.ac.at> Sender: usenet@grape.ecs.clarkson.edu In article <1991Mar07.180439.5382@nestroy.wu-wien.ac.at> mah@dec1.wu-wien.ac.at (Michael Haberler) writes: If you look at the ethernet destination address, you'll find 47:54:43 as the manufacturer code, which is hex for the string 'GTC'. Unfortunately, the first bit of 'G' is 1, so to KA9Q looks like a multicast or broadcast adress (can somebody enlighten me on this bit's meaning? Multicast (one of the many possible multicast addresses is the broadcast address). I'm going to put a check for multicast addresses into the ne1000 and ne2000 drivers for the 9.x release. -- --russ I'm proud to be a humble Quaker. It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.