From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Snooping on sockets/file descriptors
Date: Fri, 1 Apr 2011 07:19:20 +0700 [thread overview]
Message-ID: <AANLkTi=1AQqHaeKr5YhoRahAPLOj163w99m8c5ud6JeS@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinjcH=hvzdDZVCJNbrPjA08aAZ6Y8myiv8NmP=J@mail.gmail.com>
On Fri, Apr 1, 2011 at 03:04, Vimal <j.vimal@gmail.com> wrote:
> Hi Daniel,
>
>>
>> How about tcpdump?
>>
>
> Thanks for the suggestion.
>
> tcpdump is good, but it doesn't solve all problems. ?There are a few reasons:
>
> * TCP packets could arrive out of order
> * The data needn't belong to a valid TCP connection
> * The app could just discard data (close/flush/etc)
>
> In short, there is a lot of state and complex logic which act on the
> packets before it is seen by the application.
then, something like dtrace or systemtap? IMO you're looking for kinda
combo of kernel mode + user land "sniffer"... the user land sniffer,
in it's very simple form, is by using LD_PRELOAD ...
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-04-01 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimuc_tuZ9kVJU6q6CXDzE737vZYvfrKekN+SzcM@mail.gmail.com>
2011-03-31 19:29 ` Snooping on sockets/file descriptors Vimal
2011-03-31 19:58 ` Daniel Baluta
2011-03-31 20:04 ` Vimal
2011-04-01 0:19 ` Mulyadi Santosa [this message]
2011-04-01 7:23 ` Vimal
2011-04-01 13:34 ` Javier Martinez Canillas
2011-04-01 15:28 ` Vimal
2011-04-04 15:43 ` Florin Malita
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=1AQqHaeKr5YhoRahAPLOj163w99m8c5ud6JeS@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).