Re: New APIs to support multiple DLT_'s on an interface

[Guy Harris <gharris () sonic net>]

On Thu, Dec 12, 2002 at 01:04:38AM -0600, David Young wrote:
> Point taken about -D. I suggest tcpdump -y for "set data link tYpe". =)
>
> Is there any reason tcpdump cannot adopt --options ?

No technical reason I can think of.  It could not, of course, be done by
picking up GPLed argument-parsing code (unless we could get all the code
to be licensed with the "give-credit-clause-less" version of the BSD
license, and would be willing to accept GPLed code in tcpdump).

> For the sake of a consistent interface across platforms, I prefer
> that *every* tcpdump support both -L and -y. On platforms without a
> choice of DLT, however, tcpdump should not require the DLT API from
> libpcap. Instead, it should provide a trivial implementation which lists
> one DLT for -L and which insists that -y provide that DLT, only.
>
> On platforms it is implemented, pcap_list_datalinks should always return
> at least one DLT. Also, pcap_set_datalink should permit you to set at
> least any DLT on the list, but no DLT that is not on the list.

Should both of them be omitted on platforms that don't support multiple
DLT_ values per interface, or should a version of
"pcap_list_datalinks()" that returns just the p->linktype value and a
vversion of "pcap_set_datalink()" that only allows you to set the DLT_
value to p->linktype be supplied?
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:tcpdump-workers-request () tcpdump org?body=unsubscribe