Hi Rene,
I'm not getting what you want to achieve in the end. What is your tool
supposed to do with the captured and *dissected* packages? Are you
just interested in specific fields of protocols which can already be
dissected by Wireshark?
What OS are you running? On Linux/Unix - could something like (e.g.)
bash$ ssh root@myhost tshark -T fields -e ip.src -e ip.dst | ./mytool
suit your needs? This traces remotely on "myhost", extracts the source
and destination IPs and pipes the text output to the locally started
application "mytool".
Regards,
Martin
On Dec 6, 2007 10:19 AM, Baumann Rene <Rene.Baumann@xxxxxxxxxxxxxxxxx> wrote:
>
>
>
>
> Hi there,
>
> My Name is Rene and I am a Student from Germany.
> I am working on a tool, that is supposed to get the captured and dissected
> packages.
> First I need to know, if there is any API, which makes it possible to get
> the captured data from Wireshark.
> I'm thinking of a plug-in for Wireshark.
> This Plug-In should be running and send the captured data over the network
> to another computer.
> I know it is possible to programm Plug-Ins, but at the moment I know not
> much about it.
>
> May be somebody can help me. It's very important to me to know.
>
>
> Greetings from Stuttgart - Germany
>
> Rene
>
>
> 70430 Stuttgart, Germany
> Phone: +49 711 869 46606
> E-Mail: rene.baumann@xxxxxxxxxxxxxxxxx
>
> Thales Rail Signaling Solutions GmbH
> Sitz der Gesellschaft - Registered Office: Stuttgart Amtsgericht - District
> Court: Stuttgart HRB 720908
> Geschäftsführung - Managing Directors:
> Hans Leibbrand (Vorsitzender/Chairman), Manfred Riedinger
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>
