Re: need to read pcaps to develop a display system for the packets

[Abhik Sarkar <sarkar.abhik () gmail com>]

Why not write a dissector for your proprietary protocol and distribute it
only within your company only (if that's what you are about)? That would
allow you to:
- Work with the familiar interface of Wireshark and use all the facilities
available
- Use tshark to export the fields of your protocol into something like PDML
and use that XML for input into another application.

Hope that helps
Abhik.

On Mon, Feb 22, 2010 at 5:29 PM, prashanth joshi <
prashanthsjoshi2000 () yahoo com> wrote:

> Yeah. looks pretty like that for now. The basic requirement would be like
> having a utility,  to which pcaps can be input and the out put should be our
> proprietary fields of the packet displayed in a graphical format(maybe using
> c or pyhton itself.)
> But I have no clue as of now about how to proceed further. Any suggestions
> and pointers to acvance me further would be greatly appreciated.
>
> Regards,
> Prashanth
>
> --- On *Mon, 2/22/10, Jakub Zawadzki <darkjames () darkjames ath cx>* wrote:
>
>
> From: Jakub Zawadzki <darkjames () darkjames ath cx>
> Subject: Re: [Wireshark-dev] need to read pcaps to develop a display system
> for the packets
> To: "Developer support list for Wireshark" <wireshark-dev () wireshark org>
> Date: Monday, February 22, 2010, 6:01 AM
>
>
> Hello,
>
> On Mon, Feb 22, 2010 at 05:21:29PM +0530, prashanth s wrote:
> > I need to develop an application that reads a pcap as input and then
> diplays
> > the packet contents in a style that should make it easy for the reader to
> > understand - perhaps in the way wireshark does it. I have just come to
> know
> > that libcap library is used by the applications to capture packets and
> then to display them.
>
> So maybe you could write new frontend for wireshark?
> IMHO it would be great if wireshark would have ncurses frontend :)
>
> Cheers.
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark 
> org<http://us.mc544.mail.yahoo.com/mc/compose?to=wireshark-dev () wireshark org>
> >
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark 
> org<http://us.mc544.mail.yahoo.com/mc/compose?to=wireshark-dev-request () wireshark org>
> ?subject=unsubscribe
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe