From: Pedro Fortuna <pedro.fortuna@gmail.com>
To: Asim Shankar <asimshankar@gmail.com>
Cc: netdev@oss.sgi.com
Subject: Re: filtering packtes before OS takes care about them
Date: Sat, 5 Mar 2005 19:36:38 +0000 [thread overview]
Message-ID: <db95d40c050305113668c3ff07@mail.gmail.com> (raw)
In-Reply-To: <7bca1cb505030510586aeb96c1@mail.gmail.com>
Hello Asim,
I tried again but this time in Fedora Core 3 (kernel 2.6.10-1.760_FC3)
and it went flawlessly.
I have a look into your example and also into the Phrack article you
mentioned and now I'm ready to begin some tests towards what I want to
implement.
It's absolutly clear you can fetch (and modify) packets before they
are delivered to the TCP/IP stack with a custom packet_type function,
but is it also possible to intercept just before they are passed to
the network driver?
Thanks,
-Pedro Fortuna
On Sat, 5 Mar 2005 12:58:23 -0600, Asim Shankar <asimshankar@gmail.com> wrote:
> > I wasnt able to compile your packet_type_test.c :
> > all I got was a huge list of errors
> > and warnings, and no .o compiled in the end.
>
> Can you send the specific errors you got?
> And is the kernel sources present in
> /lib/modules/`uname -r`/build?
>
> Regards,
>
> -- Asim
>
next prev parent reply other threads:[~2005-03-05 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 16:16 filtering packtes before OS takes care about them Weber Matthias
2005-02-28 17:38 ` bert hubert
2005-02-28 20:09 ` Asim Shankar
2005-03-01 0:30 ` Pedro Fortuna
2005-03-01 1:53 ` jamal
2005-03-01 3:35 ` Asim Shankar
2005-03-01 16:33 ` Pedro Fortuna
2005-03-05 14:08 ` Pedro Fortuna
2005-03-05 18:58 ` Asim Shankar
2005-03-05 19:36 ` Pedro Fortuna [this message]
[not found] ` <7bca1cb50503051729e3273d3@mail.gmail.com>
2005-03-06 2:04 ` Pedro Fortuna
2005-03-07 2:46 ` Pedro Fortuna
2005-03-01 17:20 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2005-02-28 18:59 AW: " Weber Matthias
2005-03-01 0:26 ` Thomas Graf
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=db95d40c050305113668c3ff07@mail.gmail.com \
--to=pedro.fortuna@gmail.com \
--cc=asimshankar@gmail.com \
--cc=netdev@oss.sgi.com \
/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).