Andrew Gallatin writes: > > [EMAIL PROTECTED] writes: > > > Some other probes that might be useful: > <....> > > - when a packet is dropped because it is "bad" (checksum, etc) > > Speaking as driver developer for 10Gb/s NICs, it would also be nice to > somehow make snoop capture only these bad packets. I realize this is > outside the scope of dtrace, but while we are wishing for things... :)
Really, there's a wealth of things that snoop and its DLPI cohort doesn't do right or particularly well. This is just one of many. Among the others are identifying input versus output traffic, noting non-packet-related conditions (e.g., loss of carrier), retaining errored packets (runts, framing, FCS errors), and high-resolution timestamps. (Others have also mentioned a lower-overhead interface for monitoring fast networks, but I'm a little hesitant to put a performance goal in with functional issues. It could be in the list, though.) If we're going to get into snoop, I'd rather see us cast a wider net than just adding a few minor features. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
