[ale] 64 Bit Sniffit?

[Jeff Hubbs]

Hm, let's try...

cla-prodfs01 ~ # uname -a
Linux cla-prodfs01 2.6.28-gentoo-r1 #6 SMP Fri May 1 11:29:10 EDT 2009 
x86_64 Intel(R) Xeon(R) CPU E5405 @ 2.00GHz GenuineIntel GNU/Linux
cla-prodfs01 ~ # emerge -p sniffit

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] net-analyzer/sniffit-0.3.7-r1

Looks like it's there in all its 64-bit glory for the installing...

Brian Pitts wrote:
> Mike Harrison wrote:
>   
>> On Mon, 4 May 2009, James Sumners wrote:
>>
>>     
>>> You could use Wireshark. If you're unable to run it on the server, you
>>> could output the tcpdump data to a file and then import that file into
>>> your local copy of Wireshark.
>>>       
>> Yeah.. that's just a kludge.. even if I script it.
>> I just really like he way sniffit works for this level of debugging.
>> I'm just not a good enough C coder to fix sniffit for amd64.
>>
>> In the meantime, I moved my project to a 386 kernel system
>> while I debug this $!@#!@ kludge of a misconfigured Java soap server.
>>
>>     
>
> Some people, when confronted with a problem, think "I know, I'll use
> Java." Now they have two problems.
>
> More seriously, could you spare a minute to explain the advantages of
> sniffit? I've never used it before.
>
> Something very similar to James idea is to pipe the remote data directly
> to wireshark.
>
> http://wiki.wireshark.org/CaptureSetup/Pipes
>
>