Hi,
The functions tvb_length() and
tvb_reported_length() can be of use here.
Thanks,
Jaap
Send from my iPhone
On 9 jul 2010, at 00:39, eymanm wrote:
> I'm dissecting content of a UDP packet. I need to use the packet
> length number, which is IMHO is dissected by packet-udp.c. Is there
> a
On Jul 8, 2010, at 6:17 PM, Ian Schorr wrote:
> I suppose the difference here would be that you can't use the
> "contains" keyword with "opcode" to do partial string matches.
...which is an argument for supporting the "contains" operator (and the
"matches" operator) on integral data types with
I suppose the difference here would be that you can't use the
"contains" keyword with "opcode" to do partial string matches. But
that's not nearly as useful with NFSv4 as with protocols with longer,
more complex names and/or many similar names (with roughly the same
purpose) - like SMBv1.
-Ian
O
I'm dissecting content of a UDP packet. I need to use the packet length
number, which is IMHO is dissected by packet-udp.c. Is there a way of
getting this parameter within my dissector and not making any changes to
the packet-udp?
Thanks
I was always wondering, why I would need to have *two* objects for an
item containing a subtree. Doing debugging I realized, that its one and
the same object.
and both types (proto_tree/proto_item) origin in proto_node. That makes
much more sense.
Any objection to use proto_item_append_text(
The Buildbot has detected a new failure of Ubuntu-10.04-x64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/260
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: ubuntu-10.04-x64
Build R
