Wireshark · Wireshark-dev: Re: [Wireshark-dev] Get Captured Data

[sfayssal@xxxxxxxxxxxxxxxxx]

Hello:

I read in a reply that Linux version can use the T-fields, my latest
version on
fc5 0.99.4 does not support T-fields, what is the latest version for linux fc5
that does?

Thanks,

Sam

Quoting wireshark-dev-request@xxxxxxxxxxxxx:
> Send Wireshark-dev mailing list submissions to
> 	wireshark-dev@xxxxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.wireshark.org/mailman/listinfo/wireshark-dev
> or, via email, send a message with subject or body 'help' to
> 	wireshark-dev-request@xxxxxxxxxxxxx
>
> You can reach the person managing the list at
> 	wireshark-dev-owner@xxxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wireshark-dev digest..."
>
>
> Today's Topics:
>
>    1. Re: Get Captured Data (Martin Peylo)
>    2. DASS / DPNSS (Amit Khullar)
>    3. Re: DASS / DPNSS (Jaap Keuter)
>    4. Re: Help fetching values from a GtkTreeView (Stig Bjørlykke)
>    5. Apply/Prepare filter in Protocol Hierarchy (Stig Bjørlykke)
>    6. Re: Windows buildbot failing on portableapps package
>       (Gerald Combs)
>    7. error with packet.h (atdev.queries@xxxxxxxxx)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 6 Dec 2007 13:04:42 +0100
> From: "Martin Peylo" <martinmeis@xxxxxxxxxxxxxx>
> Subject: Re: [Wireshark-dev] Get Captured Data
> To: "Developer support list for Wireshark"
> 	<wireshark-dev@xxxxxxxxxxxxx>
> Message-ID:
> 	<8ca87ae60712060404r38eb1e1fy7086c8a8fefbe02a@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 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
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 6 Dec 2007 17:17:51 -0000
> From: "Amit Khullar" <Amit.Khullar@xxxxxxxxxx>
> Subject: [Wireshark-dev] DASS / DPNSS
> To: "Developer support list for Wireshark"
> 	<wireshark-dev@xxxxxxxxxxxxx>
> Message-ID: <0C3C8F1D7A866F4F9363FF3AFCBDC44AC63044@xxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
>
>
> I was wondering if DASS / DPNSS dissectors exist.
>
> Any pointers would be appreciated.
>
>
>
> Regards
>
> Amit
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://www.wireshark.org/lists/wireshark-dev/attachments/20071206/1d0c0ff3/attachment.htm
>
> ------------------------------
>
> Message: 3
> Date: Thu, 6 Dec 2007 18:44:09 +0100 (CET)
> From: "Jaap Keuter" <jaap.keuter@xxxxxxxxx>
> Subject: Re: [Wireshark-dev] DASS / DPNSS
> To: wireshark-dev@xxxxxxxxxxxxx
> Message-ID:
> 	<25300.195.193.202.94.1196963049.squirrel@xxxxxxxxxxxxxxxxx>
> Content-Type: text/plain;charset=iso-8859-1
>
> > Hi,
> >
> > I was wondering if DASS / DPNSS dissectors exist.
> > Any pointers would be appreciated.
> >
> > Regards
> > Amit
>
> Well is this your lucky day! Check out the release notes for the upcoming
> 0.99.7. It says:
> New Protocol Support
> ANSI TCAP, application/xcap-error (MIME type), CFM, DPNSS, .....
>
> So get your 'prerelease 2' here:
> http://www.wireshark.org/download/prerelease/ and let us know how it
> works.
>
> Thanx,
> Jaap
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 6 Dec 2007 19:06:34 +0100
> From: Stig Bjørlykke <stig.bjorlykke@xxxxxxxxx>
> Subject: Re: [Wireshark-dev] Help fetching values from a GtkTreeView
> To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
> Message-ID: <248D407D-33C6-4D38-8FCD-D8EC3FE67817@xxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 6. des.. 2007, at 03.14, Stephen Fisher wrote:
>
> > I haven't used GtkTreeView as a tree before, but when using it as a
> > list, you make the final field a G_TYPE_POINTER.
>
> Ah, thank you.  Now it works :)
>
>
> --
> Stig Bjørlykke
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 6 Dec 2007 19:16:17 +0100
> From: Stig Bjørlykke <stig.bjorlykke@xxxxxxxxx>
> Subject: [Wireshark-dev] Apply/Prepare filter in Protocol Hierarchy
> To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
> Message-ID: <FA2F8711-09D6-4628-9FBF-1FA21A195788@xxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
>
> Hi.
>
> I have just added Apply as / Prepare a filter in the Protocol
> Hierarchy window.
>
> Didier: you should try svn 23786.
>
>
> --
> Stig Bjørlykke
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 06 Dec 2007 12:13:32 -0800
> From: Gerald Combs <gerald@xxxxxxxxxxxxx>
> Subject: Re: [Wireshark-dev] Windows buildbot failing on portableapps
> 	package
> To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
> Message-ID: <475857EC.2090902@xxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Maynard, Chris wrote:
> > The Windows buildbot appears to be missing the now required NSIS
> > FindProcDLL plugin.  It can be obtained here:
> > http://nsis.sourceforge.net/FindProcDLL_plug-in (or here:
> > http://nsis.sourceforge.net/Find_Process_By_Name).
> >
> > Reference: http://www.wireshark.org/lists/wireshark-dev/200711/msg00009.html
> >
> > Unfortunately, every time the NSIS installer is updated, the DLL
> > will have to be manually copied to the plugin directory, as it is
> > not yet included with the NSIS installer (to my knowledge).
>
> I'll try to get the FindProcDLL plugin installed soon. In the meantime I've
> disabled the PortableApps steps on the Buildbot.
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 7 Dec 2007 16:38:13 +0530
> From: <atdev.queries@xxxxxxxxx>
> Subject: [Wireshark-dev] error with packet.h
> To: <wireshark-dev@xxxxxxxxxxxxx>
> Message-ID:
> 	<FD86B9BA6ACA984099BD817EE6933AEE11D0D0@xxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hello ,
>
> I tried including a file packet-test.c in the wireshark/plugin/test
> directory to understand the inclusion of dissection for a test
> protocol.
> But the compilation fails with the following error :
>
> Error :
> In file included from
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/proto.h:52,
>                  from
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/packet.h:37,
>                  from packet-test.c:14:
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/ftypes/ftypes.h:248: error: syntax error before
> "union"
> In file included from
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/packet.h:37,
>                  from packet-test.c:14:
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/proto.h:55:
> error: syntax error before "int"
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/proto.h:1511:
> error: syntax error before "gboolean"
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/proto.h:1515:
> error: syntax error before "int"
> In file included from
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/epan.h:33,
>                  from
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/proto.h:1531,
>                  from
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/packet.h:37,
>                  from packet-test.c:14:
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/dfilter/dfilter.h:72: error: syntax error before
> "gchar"
> ..........................................
> ..........................................
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/tfs.h:56:
> error: syntax error before "const"
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/tfs.h:57:
> error: syntax error before "const"
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/tfs.h:63:
> error: syntax error before "const"
> In file included from packet-test.c:15:
> /home/eth/plugin_dev_xxx/wireshark_32bit_test/wireshark/epan/prefs.h:156:
> error: syntax error before "e_prefs"
> make[3]: *** [packet-test.o] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
>
>
> Since these errors are pointing towards standard files( packet.h ,
> prefs.h , etc ) , could anyone please suggest what may be going wrong.
>
> Thanks in advance.
>
> Regards ,
> atdev
>
>
>
> The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of the
> addressee(s) and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately and destroy all copies of this message and any
> attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of
> viruses. The company accepts no liability for any damage caused by
> any virus transmitted by this email.
>
> www.wipro.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://www.wireshark.org/lists/wireshark-dev/attachments/20071207/9967fdda/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>
> End of Wireshark-dev Digest, Vol 19, Issue 10
> *********************************************