On Mon, May 24, 2010 at 3:54 PM, Guy Harris wrote:
>
> OK, so that's a little more complicated. There are (at least) three ways
> of handling that:
>
>1) dissect the IP rider and the custom protocol as separate
> protocols, and use the standard mechanisms for handing off from the IP rider
On May 24, 2010, at 12:18 PM, Scott wrote:
> On Mon, May 24, 2010 at 11:57 AM, Guy Harris wrote:
>> So that means that either the IP protocol rider protocol, or the custom
>> protocol, needs to have a field giving the protocol number of the protocol
>> that runs top the custom protocol. Which
Hi,
On Mon, May 24, 2010 at 01:18:00PM -0600, Scott wrote:
> I need to get at is the IP header's value for "Total Length" (ip.len). Is
> there a function for that?
packet_info->iplen
___
Sent via:Wireshark-dev mailing l
On Mon, May 24, 2010 at 11:57 AM, Guy Harris wrote:
>
> So that means that either the IP protocol rider protocol, or the custom
> protocol, needs to have a field giving the protocol number of the protocol
> that runs top the custom protocol. Which of of them has that field?
>
The IP Rider contai
On May 24, 2010, at 9:40 AM, Scott wrote:
> Hi Guy! I hope your weekend was enjoyable.
Thanks! I hope yours was enjoyable, too.
> On Sat, May 22, 2010 at 2:39 PM, Guy Harris wrote:
>> So presumably the IP protocol rider protocol has fields of its own.
>>
>> Does the IP protocol rider have a
Hi Guy! I hope your weekend was enjoyable.
On Sat, May 22, 2010 at 2:39 PM, Guy Harris wrote:
> So presumably the IP protocol rider protocol has fields of its own.
>
> Does the IP protocol rider have an IP protocol number assigned to it, so
> that you have:
>link-layer protocol
>
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Scott
Sent: Friday, May 21, 2010 1:50 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Sub_dissectors assertion failed
Thanks for the reply
On May 21, 2010, at 6:42 PM, Scott wrote:
> On Fri, May 21, 2010 at 3:18 PM, Guy Harris wrote:
>> So what protocols does your custom protocol run on top of?
>
> For now the custom protocol is a dummy protocol that only contains a 32-bit
> int and rides on top of the IP protocol rider (*it*).
On Fri, May 21, 2010 at 3:18 PM, Guy Harris wrote:
>
> So what protocols does your custom protocol run on top of?
For now the custom protocol is a dummy protocol that only contains a 32-bit
int and rides on top of the IP protocol rider (*it*). I got the custom
protocol to show up in the packet
On May 21, 2010, at 12:49 PM, Scott wrote:
> I killed the original error of
> ERROR:packet.c:709:dissector_add: assertion failed: (sub_dissectors)
> by calling register_dissector_table() in proto_register_..(). Apparently I
> didn't know I needed to do that, but it makes sense.
Yes. As indica
Thanks for the reply Guy! I have some followup questions.
I killed the original error of
ERROR:packet.c:709:dissector_add: assertion failed: (sub_dissectors)
by calling register_dissector_table() in proto_register_..(). Apparently I
didn't know I needed to do that, but it makes sense.
To answer
On May 20, 2010, at 5:58 PM, Scott wrote:
> If I am writing a dissector for a protocol that rides on top of IP but then
> allows any protocol to follow it,
Do you truly mean "any protocol", so that, for example, you could follow it
with X.25 or HTTP or Ethernet, or do you mean, for example, an
Devs,
This post pertains to two (probably) interrelated things.
If I am writing a dissector for a protocol that rides on top of IP but then
allows any protocol to follow it, how do I register them all correctly with
my dissector? I see that IP does this by enumerating protocol numbers in
ipproto
13 matches
Mail list logo
