What are you talking about? It's Wednesday. Everyone knows that UTF8Strings
have indefinite lengths on Wednesdays.
On Dec 15, 2010, at 8:50 AM, Jaap Keuter wrote:
> Hi,
>
> "With the proper use of subtrees the structure of even the most complex
> protocols becomes clear."
> ... and then came AS
Hi,
"With the proper use of subtrees the structure of even the most complex
protocols becomes clear."
... and then came ASN.1 ... ;)
Thanks,
Jaap
On Wed, 15 Dec 2010 17:32:13 +0100, "news.gmane.com"
wrote:
> "Jaap Keuter" wrote in
> message news:75883c052eaf82074dac3aef04d29...@xs4all.nl...
>
"Jaap Keuter" wrote in
message news:75883c052eaf82074dac3aef04d29...@xs4all.nl...
> Hi,
>
> This 'colorize' is mainly intended to mark changeover into another
> protocol.
> Usually you see this at the top level (from the root), but occasionally
> when a protocol is encapsulated (some ITU protoco
Hi,
This 'colorize' is mainly intended to mark changeover into another
protocol.
Usually you see this at the top level (from the root), but occasionally
when a protocol is encapsulated (some ITU protocols show this).
As long as your 'structures' are at the top level, these could be
considered vali
When I look at other dissector's output they use the
proto_tree_add_protocol_format only for indicating that a new protocol is
engaged.
These protocol lines in the tree are also displayed in other colors. That
makes it easy to navigate by eyes. I have a protocol with a lot of
structures inside. Wh
