Hi,
Thanks a lot. It is not the first time I have got non-binary snoop files and probably not the last one, so it's good to have a working perl-script next time it happens.
I will try you script out and do modifications to it if needed.
They sent the original file just before they left work late Friday evening (their timezone), but they contacted
me early Saturday morning (my timezone) just before I had started writing a conversion program.
It was possible for me to get some new captures in binary snoop format without any problem this time.
Best regards,
Martin
-----Original Message-----
From: Alistair.McGlinchy@xxxxxxxxxxxxxxxxxxxxx <Alistair.McGlinchy@xxxxxxxxxxxxxxxxxxxxx>
To: martin.regner@xxxxxxxxx <martin.regner@xxxxxxxxx>
Cc: ethereal-users@xxxxxxxxxxxx <ethereal-users@xxxxxxxxxxxx>
Date: Monday, March 03, 2003 11:15 PM
Subject: RE: [Ethereal-users] Non-binary Snoop-file
>
>
>> -----Original Message-----
>> From: Martin Regner [mailto:martin.regner@xxxxxxxxx]
>> Sent: 28 February 2003 22:03
>> To: ethereal-users@xxxxxxxxxxxx
>> Subject: [Ethereal-users] Non-binary Snoop-file
>>
>>
>> Is there any easy way of converting a non-binary snoop-file
>> so that it can be readable by Ethereal?
>
>I've no idea what the in-between frames text looks like. But the following
>Perl script worked for me on your source data.
>
>open OUT, "| text2pcap.exe - $ARGV[0]" or die "Cannot create pipe $!";
>while(<DATA>) {
> s/([0-9a-f]{2})([0-9a-f]{2}) /$1 $2 /g;
> s/^\s*(\d+)\:/sprintf(qq(%04x),$1)/e;
> print OUT $_
>}
>close OUT;
>
>__DATA__
> 0: 0001 7151 ffe7 8811 22fa dd38 0800 4500 ..PPq... .-8..E.
> 16: 0028 9911 4000 3c66 8880 ee1e 03cf ee10 .(..@.<.........
> 32: 01ce
>