Re: DLT_ request

[Guy Harris <guy () alum mit edu>]

marc hermstein wrote:
> When developing a handset, some manufacturers dump
> debugging data from the protocol stack out the serial
> port on the bottom of the handset. This is what I
> meant by a "logger".

So you'll be writing, or have written, a piece of code that reads from 
the serial port and writes to a libpcap file?  Or is there already 
software that logs the debugging data in another format (in which case 
you might be able to modify Ethereal's Wiretap library to read those files)?

It might be interesting to add to libpcap a module to do live captures 
on a serial port.  There will probably be other types of capturing 
people would want to do on serial ports, so there might eventually be a 
generic "serial port" capture module supporting multiple DLT_ types. 
There might have to be a way to specify the baud rate, bits per 
character, parity, etc. - the current "pcap_open_live()" API can't do 
that, but I'm thinking of a future open API that'd take an 
attribute/value list of options (so that it could, for example, have 
options to support "monitor mode" and setting the channel for 802.11), 
so that the option list could be extended without API changes (there 
might also be a way to find out what devices offer what options, so that 
applications such as Ethereal could offer GUI options).

However, some or all of the serial port settings might be implied by the 
protocol, in which case they wouldn't have to be specified.
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.