From: Jeff Dike <jdike@karaya.com>
To: Andreas Kinzler <akinzler@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Injecting packets into the kernel
Date: Sat, 22 Dec 2001 17:11:49 -0500 [thread overview]
Message-ID: <200112222211.RAA08992@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Sat, 22 Dec 2001 21:22:06 +0100." <20011222202340Z282222-18284+6230@vger.kernel.org>
akinzler@gmx.de said:
> but the packets written to such a device have no effect, they do not
> seem to make their way through the kernel.
Hmmm, well that's exactly what UML does and its packets are treated in
exactly the way you seem to want. They are treated as coming from a totally
different machine (although UML, as a complete machine, has a complete network
stack, network devices with their own IP addresses, etc, so you might just
not be making your packets look "remote" enough).
Jeff
next prev parent reply other threads:[~2001-12-22 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 20:22 Injecting packets into the kernel Andreas Kinzler
2001-12-22 22:11 ` Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-22 18:26 Andreas Kinzler
2001-12-22 20:57 ` Jeff Dike
2001-12-22 16:50 Andreas Kinzler
2001-12-22 16:54 ` Andreas Steinmetz
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=200112222211.RAA08992@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=akinzler@gmx.de \
--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