Ethereal-dev: [Ethereal-dev] Preference reasemble TCP on or off ( was Use of tcp_dissect_pdu a
Hi,
I still think it would be preferable to have the option default on ( and leave the subdissectors prefs on as well )
as this probably would cause less confusion for new users, experienced users probably knows enough
to be able to turn it off.
Olivier wrote:
>--Snip---
>Mmh... This may be a potentially memory-hungry thing to do. Maybe we have to
>add a note to protocols running on top of TCP that they need to enable the
>"Reassemble TCP" option. Could this be done automatically in the preferences
>module?
>
>Maybe we also want to have a list with the most common preferences grouped
>together, and then we could toggle between "standard mode" and "expert mode"
>:)
>
>There's still one thing I want to have in Ethereal: startup tips. Does
>anyone know a good implementation for this?
--- snip ---
Would that be a big problem ? - you can still turn the pref. off ( if you know it's there ).
Best regards
Anders
-----Original Message-----
From: Guy Harris [mailto:guy@xxxxxxxxxxxx]
Sent: den 23 januari 2004 20:08
To: Ronnie Sahlberg
Cc: CNS - Matthew Bradley; ethereal-dev@xxxxxxxxxxxx; Anders Broman
(TN/EAB)
Subject: Re: [Ethereal-dev] Use of tcp_dissect_pdu and tvb_format_text
On Jan 23, 2004, at 3:35 AM, Ronnie Sahlberg wrote:
> I think it would make a lot of sense if someone did a patch to change
> TCP offser reassembly : to default to on
> and change all subdissector requesting tcp reassembly to off.
Unfortunately, that still means you have to do something to enable
reassembly - and now you have to enable it for a lot of protocols,
rather than just being able to enable it from the TCP preference
setting.
> I am now working on a packet-ber.c helper (dissect BER constructs,
> tabledriven and similar to packet-per.c) to be used to
> dissect asn1/ber encoded data using ethereal native code
We use native code now - asn1.c (It came from GXSNMP, but it's not a
third-party library.)
However, having packet-per.c-style helpers for BER would probably be
better, especially if it has, as I understand packet-per.c has, a
preference setting to show the internal encoding information for items.
