Re: [Wireshark-dev] Setting to disable all expert info

[Dario Lombardo]

On Wed, Aug 2, 2017 at 10:21 PM, Guy Harris  wrote:

>
> Let's wait until the generation of the expert info results in a measurably
> significant CPU or memory use increase before we add a knob to turn it
> off.  There are probably other places to look at to reduce memory usage
> first.
>

That's an interesting point... any idea what they are?
I worked on the conversation code that looks one of the most memory eaters.
I was working on purging pending conversations after a while. The idea was
that if I can't find the corresponding packet of a conversation in a bunch
of seconds (let's say 5), it is very unlikely that I will find it. I am
aware that some protocols could have looser timing constraints and this
approach wouldn't work for them, but I was just playing with the idea. What
do you think?
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV data types

[Paul Offord]

I've realised below is a stupid idea.  I was trying to be clever by picking 
numbers that spelt out the block type in a hex dump of a file, but I've 
realised this is of little use.  I'll use:

•   0x0010 – Text Source Descriptor Block (TSDB)
•   0x0011 – Text Source Record Block (TRB)

This leaves some space for base types.

Best regards...Paul

-Original Message-
From: Paul Offord 
Sent: 25 July 2017 10:36
To: Developer support list for Wireshark 
Subject: RE: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV 
data types

Hi,

Sorry - Slight amendment.

Can I register two new PCAP-NG block codes?  I’d like:

•   0x42445354 – Text Source Descriptor Block (TSDB)
•   0x00425254 – Text Source Record Block (TRB)

What do I need to do to register these?

See below for the reason for request.

Thanks and regards…Paul

-Original Message-
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of 
Paul Offord
Sent: 25 July 2017 10:26
To: Developer support list for Wireshark 
Subject: Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV 
data types

Hi,

Can I register two new PCAP-NG block codes?  I’d like:

•   0x54534442 – Text Source Descriptor Block (TSDB)
•   0x54524200 – Text Source Record Block (TRB)

What do I need to do to register these?

See below for the reason for request.

Thanks and regards…Paul


-Original Message-
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of 
Guy Harris
Sent: 19 June 2017 22:54
To: Developer support list for Wireshark 
Subject: Re: [Wireshark-dev] Adding support to Wireshark for CSV, TSV and SSV 
data types

On Jun 19, 2017, at 3:06 AM, Paul Offord  wrote:

>> Do you mean "deal with arbitrary CSV and TSV files" or "deal with IIS Web 
>> logs that are in CSV and TSV format"?
> 
> Yes - I mean arbitrary comma, tab and space separated.

I think Microsoft have an Excellent program that reads CSV files - and possibly 
TSV and SSV as well - and lets you do various forms of processing on them; it's 
available for Windows and macOS.  I think there's another program called 
LibreOffice Calc that's available for those platforms and for Linux, *BSD, and 
other OSes as well.

I.e., what does *Wireshark* provide here, for the *general* case of CSV/TSV/SSV 
files, that a spreadsheet program doesn't?

> Going back to the main objective, what I'm proposing is that we enable a 
> PCAP-NG file to contain any text-based data together with a schema - JSON or 
> XML or PCAP-NG proprietary.  There would be one WTAP_ENCAP_xxx type for any 
> text-based data type. Decoding would be based on the schema data.

pcapng, unlike pcap, can have blocks in it that *don't* correspond to packets.  
What's needed here are new pcapng block types:

a "text source description block" (TSDB), which contains a schema and 
options (such as comments);

a "text record block" (TRB), which contains:

a "text source ID", which indicates which TSDB corresponds to 
the source of the record (the first TSDB has an ID of 0, the next one an ID of 
1, etc., along the lines of Interface Description Blocks);

the text;

options (such as comments).

This would *not* require a DLT_/LINKTYPE_ or a WTAP_ENCAP_ value.  It would 
also allow packets and text records to be combined into one file.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

__

This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not 
necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be 
guaranteed to be secure or error-free as information could be intercepted, 
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The 
sender therefore does not accept liability for any errors or omissions in the 
contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour 
House, Coopers End Lane, Stansted, Essex CM24 1SJ

__
This email has been scanned by the Symantec