All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Johan Bostorp <ctor@krixor.xy.org>
To: netdev@oss.sgi.com
Subject: Re: packet socket can't steal packets
Date: Wed, 3 Jan 1990 21:25:00 +0100	[thread overview]
Message-ID: <19900103212500.A4614@ratula.chimaira.se> (raw)
In-Reply-To: <Pine.OSF.4.30.0205072042410.30796-100000@kosh.hut.fi>; from dima@cc.hut.fi on Tue, May 07, 2002 at 09:02:31PM +0300

On Tue, May 07, 2002 at 09:02:31PM +0300, Dmitrii Tisnek wrote:
> hey, I've been trying to change certain network packet mangling software
> such that it would not need a kernel module, and it seems to me that,
> unfortunately there's no way to make packet socket "steal" packets it
> deliveres to the user mode.

"Divert Sockets for Linux" springs to my mind.. 

http://www.anr.mcnc.org/~divert/index.shtml

---
   Divert sockets enable both IP packet interception and injection on the
   end-hosts as well as on routers. Interception and injection happen at
   the IP layer. The intercepted packets are diverted to sockets in the
   user space, thus they will not be able to reach their destination
   unless they are reinjected by the user space sockets. This allows
   different tricks (e.g., routing and firewall) to be played, outside
   the operating system kernel, in between the packet interception and
   reinjection.
---


-- 
~~~<*>~~~

Web: http://elemental.webservices.se/		   ICQ: 3534707
PGP: 0xA6B5C43B					IRCnet: ctor

~~~<*>~~~

  reply	other threads:[~1990-01-03 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 18:02 packet socket can't steal packets Dmitrii Tisnek
1990-01-03 20:25 ` Carl-Johan Bostorp [this message]
2002-05-08 13:49   ` Chris Friesen
2002-05-07 18:16 ` Thomas 'Dent' Mirlacher
2002-05-07 18:28   ` Dmitrii Tisnek
2002-05-07 18:39     ` Thomas 'Dent' Mirlacher

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=19900103212500.A4614@ratula.chimaira.se \
    --to=ctor@krixor.xy.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.