Fulko Hew wrote:
So in the end... I think I'd rather continue persuing this single DLT
approach
where I can embed status/signalling stuff into a single dissector
IE. Have a pcap with DLT_ACN_WAN and dissectors for:
ACN_WAN (that handles signal/status info and then dispatches to:)
Frame
Michael Richardson wrote:
Gianluca> Wasn't there supposed to be a x.9.7 release due a couple
Gianluca> weeks ago, fixing the issue?
That was my plan.
The tcpdump 3.9.6 archive still appears to contain tcpdump 3.9.5.
Any plans to take this forward? Or a rough time estimate of when
On 7/17/07, Guy Harris <[EMAIL PROTECTED]> wrote:
Fulko Hew wrote:
> a given capture will only ever have a single protocol within it,
> but since the header is common for all protocols, I thought it was
> better to
> ask for a single DLT instead rather than one DLT per protocol.
Not necessarily
Fulko Hew wrote:
a given capture will only ever have a single protocol within it,
but since the header is common for all protocols, I thought it was
better to
ask for a single DLT instead rather than one DLT per protocol.
Not necessarily - DLTs are cheap, and Wireshark already has, for
exam
On 7/17/07, Guy Harris <[EMAIL PROTECTED]> wrote:
Fulko Hew wrote:
> I am formally requesting a new DLT value to support capture traffic
> from my companies
So that'd be SITA:
http://www.sita.aero/default.htm
Correct.
> LAN/WAN router/protocol converter device.
>
> Since this device
Fulko Hew wrote:
I am formally requesting a new DLT value to support capture traffic
from my companies
So that'd be SITA:
http://www.sita.aero/default.htm
LAN/WAN router/protocol converter device.
Since this device supports WAN protocols, this new DLT will be
used to provide/indicat
I am formally requesting a new DLT value to support capture traffic
from my companies LAN/WAN router/protocol converter device.
Since this device supports WAN protocols, this new DLT will be
used to provide/indicate that the data stream contains a
number of WAN port specific pieces of information
