From: "Lanfranco Salinari" <lanfranco.salinari@icn.siemens.it>
To: "Abraham vd Merwe" <abraham@2d3d.co.za>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Question about sniffers and linux
Date: Mon, 10 Dec 2001 14:38:36 +0100 [thread overview]
Message-ID: <000901c18180$01bac960$11b41d8d@icn.siemens.it> (raw)
In-Reply-To: <3BEC87A2@webmail> <20011210100918.E1502@crystal.2d3d.co.za>
----- Original Message -----
From: Abraham vd Merwe <abraham@2d3d.co.za>
To: salinarl <Lanfranco.Salinari@icn.siemens.it>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Sent: Monday, December 10, 2001 9:09 AM
Subject: Re: Question about sniffers and linux
>Hi salinarl!
>
>You don't need to write a kernel module to do this.
>
>Use RAW sockets. (See man 2 socket). If you're not interested in the link
>layer, you can also use DGRAM sockets to get everything from layer 3 and up
>(ip, arp, etc.)
>
Thank you for your answer, Abraham!
Perhaps I did not explain myself very well: I know about RAW sockets, but
the problem is that, for example, PPP headers are not passed to packet
sockets (for outgoing packets), because they are added inside the PPP driver
after the call to dev_queue_xmit_nit().
I don't know if this problem is typical of PPP, but it seems quite general,
to me. I think Ethernet headers are a special case, because they are taken
from a
cache and added in the IP layer, so they are visible to packet sockets.
Can someone please tell me if I'm wrong?
Best regards,
Lanfranco
prev parent reply other threads:[~2001-12-10 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 18:44 salinarl
2001-12-10 8:09 ` Abraham vd Merwe
2001-12-10 13:38 ` Lanfranco Salinari [this message]
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='000901c18180$01bac960$11b41d8d@icn.siemens.it' \
--to=lanfranco.salinari@icn.siemens.it \
--cc=abraham@2d3d.co.za \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®