On Mar 2, 2011, at 7:49 AM, Schemmel, Hans-Christoph wrote:
> I just want to ask if you´ve already assigned a DLT value for the dissector?
Not yet - I've been somewhat busy the past week and a half, and I have to
condense all the e-mail on this thread into a complete and precise description
of
I just want to ask if you´ve already assigned a DLT value for the dissector?
Kind regards,
Christoph Schemmel
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
Guy Harris alum.mit.edu> writes:
>
> The PPP chunks are indicated by the {Msg_ID, Freq_ID, Start_Pos, End_Pos,
Flag} quintuplets, where
> Start_Pos is the 1-origin index (i.e., the first byte of the MUX_Frame has an
index of 1, not 0), from the
> beginning of MUX_Frame, of the first byte of the
On Feb 14, 2011, at 6:26 AM, Schemmel, Hans-Christoph wrote:
> Yes, Start_Pos and End_Pos are relative to the beginning of the MUX_Frame,
> but a
> PPP chunk does not start directly at the beginning of a MUX_Frame
> (Start_Pos=0).
> The PPP frame starts after the header fields of the MUX_Frame.
Guy Harris alum.mit.edu> writes:
>
> Start_Pos and End_Pos are relative to the beginning of MUX_Frame, right?
I.e., a 4-byte chunk starting at
> the beginning of MUX_Frame would have a Start_POS of 0? Would End_POS be 3
(meaning that it's the offset of
> the last byte of the chunk) or 4 (meani
On Feb 4, 2011, at 1:59 AM, Schemmel, Hans-Christoph wrote:
> Guy Harris alum.mit.edu> writes:
>
>>
>> OK, so it's:
>>
>> Header_Size: 1 octet
>>
>> A sequence of zero or more instances of:
>>
>> Msg_ID: 2 octets
>>
>> Freq_ID: 2 octets
>>
>>
Guy Harris alum.mit.edu> writes:
> should I just describe the holes as "other data", so you're not
> constrained to forever make them all be AT command/response text, or is it
guaranteed (now and forever) to
> be AT-command-or-response text?-
The description of the holes as "other data" sounds
On Feb 4, 2011, at 1:59 AM, Schemmel, Hans-Christoph wrote:
> The parts that don´t correspond to a PPP packet are AT commands or responses
> (like "ATI", "AT+CSQ" or "+CSQ: 18,99"). This content is interpreted and
> displayed as raw text in the Wireshark subtree for the payload/information of
>
Guy Harris alum.mit.edu> writes:
>
> OK, so it's:
>
> Header_Size: 1 octet
>
> A sequence of zero or more instances of:
>
> Msg_ID: 2 octets
>
> Freq_ID: 2 octets
>
> Start_Pos: 1 octet
>
> End_Pos: 1 octet
>
>
On Feb 3, 2011, at 2:05 AM, Schemmel, Hans-Christoph wrote:
> I´ve mixed up some field sizes in my previous mail. Msg_ID and Freq_ID have a
> size of 2 octects, not 1 octect like the other fields, sorry. So the optional
> part has a size of 7 octects. But your conclusion is correct: The Header_Si
Guy Harris alum.mit.edu> writes:
> OK, so the Direction field and Header_Size fields are always present, and the
Header_size field gives the
> size of the *optional* fields; if a frame contains N PPP packets, the
Header_Size field has the value 5N.
> (If Header_Size isn't a multiple of 5, the fr
On Jan 26, 2011, at 2:30 AM, Schemmel, Hans-Christoph wrote:
> The size of the header depends on the number of PPP packets in the payload of
> the MUX frame. The Header_Size indicates whether Msg_ID, Freq_ID, Start_Pos,
> End_Pos, and Flag are present.
> For example:
> The header of a frame witho
Guy Harris alum.mit.edu> writes:
>
> So are any of those fields optional? For example, is the fragment ID
optional? If so, what indicates whether
> it's present? If nothing is optional, why is the header size not always 7?
>
The size of the header depends on the number of PPP packets in th
On Jan 20, 2011, at 3:05 AM, Schemmel, Hans-Christoph wrote:
> The format of the additional header is:
>
> | Header_Size | Msg_ID | Freq_ID | Start_Pos | End_Pos | Flag | ... |
> Msg_ID |
> Freq_ID | Start_Pos | End_Pos | Flag | Direction | MUX_Frame
>
> Header_Size (1 Octet): Total length
Guy Harris alum.mit.edu> writes:
>
> What is the format of the additional header?-
The format of the additional header is:
| Header_Size | Msg_ID | Freq_ID | Start_Pos | End_Pos | Flag | ... | Msg_ID |
Freq_ID | Start_Pos | End_Pos | Flag | Direction | MUX_Frame
Header_Size (1 Octet): To
Guy Harris alum.mit.edu> writes:
>
> OK, so it sounds as if this isn't raw standard 27.010 traffic. Is MUX27010
likely to be used as a name for that
> traffic? If not, we could call it DLT_MUX27010/LINKTYPE_MUX27010.
>
> What is the format of the additional header?-
> This is the tcpdump-work
On Jan 17, 2011, at 5:52 AM, Schemmel, Hans-Christoph wrote:
> Concerning dissecting: The communication between GSM modem and the host is
> captured with an USB Tracer. The tracer uses a proprietary format for the
> trace
> files, but the data of these files can be exported, e.g. as csv file. I´
> Is this DLT value only for the Basic Option, or is it also used for the
Advanced Option? If it's also for the
> Advanced Option:
>
> 1) Is the flag octet 0x7E if the Advanced Option is being used?
>
> 2) If the Advanced Option is being used, do the packet contents include
escape oc
On Jan 12, 2011, at 4:59 AM, Schemmel, Hans-Christoph wrote:
> A packet begins with a flag (octet 0xF9, section 5.2.1.1), followed by address
> and control field.
Is this DLT value only for the Basic Option, or is it also used for the
Advanced Option? If it's also for the Advanced Option:
Guy Harris alum.mit.edu> writes:
>
>
> On Jan 10, 2011, at 6:16 AM, Schemmel, Hans-Christoph wrote:
>
> > I´ve written a dissector (MUX27010) for wireshark and I want to commit it to
the project. Therefore I need
> a new DLT value for this dissector/protocol because the protocol doesn´t base
u
On Jan 10, 2011, at 6:16 AM, Schemmel, Hans-Christoph wrote:
> I´ve written a dissector (MUX27010) for wireshark and I want to commit it to
> the project. Therefore I need a new DLT value for this dissector/protocol
> because the protocol doesn´t base upon another data link layer protocol.
> Wh
Hi,
I´ve written a dissector (MUX27010) for wireshark and I want to commit it to
the project. Therefore I need a new DLT value for this dissector/protocol
because the protocol doesn´t base upon another data link layer protocol.
What the dissector does: It analyses a multiplexed communication bet
22 matches
Mail list logo
