> From: David Greenman <dg@root.com>
> Date: 1999-06-27 14:07:31 -0700
> To: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
> Subject: Re: excessive promiscuity in i82557/fxp driver?
> Cc: tech-net@netbsd.org, "Christian E. Hopps" <chopps@merit.edu>
> In-reply-to: "Your message of Sun, 27 Jun 1999 16:24:16
> EDT."<199906272024.UAA23651@orchard.arlington.ma.us>
> Delivered-to: tech-net@netbsd.org
>
> > ...
> >"prm" is 1 if the device is being put into promiscuous mode, 0
> >otherwise.  Is there any particularly good reason to do this sort of 
> >thing by default? (i.e., does promiscuous mode lose valid frames on 
> >the fxp unless you also tell the chip to receive broken frames and 
> >runts?)
>
>    The idea is that promiscuous mode is often used to diagnose network 
> problems, and thus should allow certain types of shouldn't-happen  
packets
> through (such as too small).
  Shouldn't this be a separate function?  Overloading promiscuous  
mode seems like the wrong thing to do.  E.g., AIX has such an  
interface to their network drivers, and we're looking at a similar  
issue for Mac OS X.  I'm not wild about AIX's API, BTW.

Regards,

Justin

--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics       |
Manager, CoreOS Networking            | When crypto is outlawed,
Apple Computer, Inc.                  | Only outlaws will have crypto.
2 Infinite Loop                       |
Cupertino, CA 95014                   |
*-------------------------------------*-------------------------------*