On Jan 17, 2017, at 5:25 AM, Becker (ELZET80) <bec...@elzet80.de> wrote:
> I think my request was a bit misleading and wrong formulated. I told you we
> are working on a BITBUS tracer which in reality is a SDLC tracer that can
> trace BITBUS too.
So by "tracer" do you mean that it actually dissects and displays packets, or
do you mean it captures packets and feeds them to Wireshark or some other
program to dissect?
>>> Is there a way to use the SDLC dissector as a DLT already?
>> No, and if you were to do so, you probably wouldn't like the results, unless
>> you're using SNA on the BITBUS links.
>>
>>> If not we would request a DLT for SDLC communication on which we would base
>>> our BITBUS lua dissector plugin.
>>
>> You should, instead, get LINKTYPE_BITBUS/DLT_BITBUS.
>
> I don't think thats what we want as we have raw SDLC frames coming from our
> usb tracer and need to display them too.
So what's a "raw SDLC frame"? An SNA packet using SDLC as the link-layer?
> We want to feed the data directly into Wireshark with an extcap component and
> don't want to go the detour over ethernet packets.
> The payload data should not be interpreted by default (we would write a lua
> bitbus dissector for that).
So are these BITBUS packets, SNA packets, or both?
("SDLC" isn't "any protocol with an address field and an SDLC-like control
field"; that definition would include HDLC, LAPB, LAPD, BITBUS, etc..)
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
