Re: Regarding wireshark design

[ronnie sahlberg <ronniesahlberg () gmail com>]

Perhaps the answer can be found in the documentation ?


On Thu, May 10, 2012 at 9:28 PM, Singh, Anand <Anand.Singh () landisgyr com> wrote:
> Hi,
>                Can you please let me know how does it talk with raw packets. Is it using existing TCP stack or is it 
> directly communication with lower level drivers like phy/Mac layer. & Where do I find that code section where we 
> accessing raw buffers.
>
> Regards
> Anand
>
> -----Original Message-----
> From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of ronnie 
> sahlberg
> Sent: Thursday, May 10, 2012 4:29 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Regarding wireshark design
>
> There are READMEs in the doc subdirectory.
>
> README.developer is a good starting point.
>
>
> Otherwise, most of the code is pretty straightforward so it shouldnt be too hard to just read it.
>
>
>
> On Thu, May 10, 2012 at 8:52 PM, Singh, Anand <Anand.Singh () landisgyr com> wrote:
> > Hi,
> >
> >                   Can anyone give me thorough reference on how exactly
> > wireshark work while displaying packet on linux. Where do I start to
> > get insights of design of wireshark. What is the code flow, from which
> > file I start browsing the code. I will greatly help me understand
> > wirshark existing code & enhance the code for my usage.
> >
> >
> >
> > Regards
> >
> > Anand
> >
> >
> >
> >
> >
> > P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL.
> >
> > This e-mail (including any attachments) is confidential and may be
> > legally privileged. If you are not an intended recipient or an
> > authorized representative of an intended recipient, you are prohibited
> > from using, copying or distributing the information in this e-mail or its attachments.
> > If you have received this e-mail in error, please notify the sender
> > immediately by return e-mail and delete all copies of this message and
> > any attachments. Thank you.
> >
> >
> > ______________________________________________________________________
> > _____ 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
>
>
> ___________________________________________________________________________
> 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