Re: [ethereal-dev] Question

[Ashok Narayanan <ashokn@xxxxxxxxx>]

> This is similar to what, for example, Microsoft's Network Monitor does.
> 
> Given that, the reason to give different tree types different ETT_
> values is to arrange that opening one kind of tree doesn't cause trees
> of another type to be opened if you then go to another packet.

...and I just found that out. Hadn't tried switching to another packet
while the previous packet was open. Oh well...

Which brings me to the next two questions:

1) How scarce is ETT_ space? Given that there are 16 different types of
RSVP objects, can I use up 18 entries in the ETT_ list? For a
going-forward basis, should a different approach be considered? e.g.
have a special class of tree which is not persistently open across
packets.

2) Is there a reader for the MS Netmon capture file format? If not,
anybody working on one?

-Ashok


-- 
--- Ashok Narayanan ----------------------------------------
IOS Network Protocols, Cisco Systems
250 Apollo Drive, Chelmsford, MA 01824
Ph: 978-244-8387