Newsgroups: comp.dcom.sys.cisco
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!barmar
From: barmar@think.com (Barry Margolin)
Subject: Re: broadcast leakage
Message-ID: <1991Apr30.171838.15805@Think.COM>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
References: <34652@boulder.Colorado.EDU> <1991Apr30.151949.22646@unlinfo.unl.edu>
Date: Tue, 30 Apr 91 17:18:38 GMT

In article <1991Apr30.151949.22646@unlinfo.unl.edu> mosemann@unl.edu writes:
>   Even after the problem was known, it was low priority.  The
>recommended solution was to not have our machines send to their MAC
>address if it was an IP broadcast packet.

I'm curious -- why are your hosts sending IP broadcasts to the MAC address
of the router instead of the MAC broadcast address?  It sounds to me like
your hosts are doing the wrong thing.  Are you giving the vendors of the
host IP software as much shit as you're giving cisco?

--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar
