Ethereal-users: RE: [Ethereal-users] Can Ethereal export in CSV format

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Dirk" <dirk@xxxxxxxxxxxxxxx>
Date: Tue, 20 Jul 2004 11:08:35 -0000
Hi,
This is how Sniffer does the export, and that would suffice.

"Flags","Frame","Delta Time","Size","Destination","Source", "Protocol",
"Summary"
"M", 3284, 0.000 , 446,"Server","Client","TCP","D=1521 S=2130 ACK=...."
" ", 3285, 0.002 , 94,"Client","Server","TCP","D=2130 S=1521 ACK=...."
" ", 3286, 0.000 , 89,"Server","Client","TCP","D=1521 S=2130 ACK=...."
" ", 3287, 0.010 , 605,"Client","Server","TCP","D=2130 S=1521 ACK=...."
" ", 3288, 0.002 , 299,"Server","Client","TCP","D=1521 S=2130 ACK=...."
" ", 3289, 0.001 , 91,"Client","Server","TCP","D=2130 S=1521 ACK=...."
" ", 3290, 0.000 , 82,"Server","Client","TCP","D=1521 S=2130 ACK=...."
" ", 3291, 0.003 , 155,"Client","Server","TCP","D=2130 S=1521 ACK=...."
" ", 3292, 0.001 , 75,"Server","Client","TCP","D=1521 S=2130 ACK=...."
" ", 3293, 0.001 , 73,"Client","Server","TCP","D=2130 S=1521 ACK=...."
" ", 3294, 0.002 , 446,"Server","Client","TCP","D=1521 S=2130 ACK=...."

Better still would be the addition of a few more columns to break out the
summary field and have Sequence numbers and Ack numbers as well as source
and destination ports in seperate columns.

Regards

Dirk Loosen
IT Ecology
dirk@xxxxxxxxxxxxxxx
Tel: (011) 391 3330
Cell: 082 575 4931



-----Original Message-----
From: Guy Harris [mailto:gharris@xxxxxxxxx]
Sent: 20 July 2004 02:07 AM
To: Dirk
Cc: ethereal-users@xxxxxxxxxxxx
Subject: Re: [Ethereal-users] Can Ethereal export in CSV format


Dirk said:
> Secondly I am looking for functionality that will export the packet trace
> informtion similar to the txt export but in a format that I can easily
> import into a database. The current format doesn't seperate well CSV file
> or similar.

Ethereal currently doesn't support that.

If somebody provided a detailed specification of what would be in the CSV
file, it might be implemented at some point; the problem is that there's a
*lot* of information in the decoded packet trace, so a specification such
as "write out the columns of the summary in CSV format" or "let the user
specify a list of named fields, and export the *first* occurrence of each
of those named fields in a packet in CSV format" would be needed.