> | Obviously there are thousands of OUIs, and most are not going to ever > | be in tcpdump's list, and it seems like populating oui.c with 20,000 > | OUIs may not be the way to go.
> | Thoughts? > > make it better ;-) - what do you suggest ? - pull in a OUI table frequently ? How about loading it from a local file that is updated externally? That's how PCI and USB IDs are updated on many systems, and that's how arpwatch gets its OUIs already (ethercodes.dat - vendor ethernet block list). It is simple and allows local changes. Allowing to share the file between tcpdump and arpwatch would be nice. Michael _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
