From: Ben Greear <greearb@candelatech.com>
To: Michael Renzmann <mrenzmann@web.de>
Cc: netdev@oss.sgi.com
Subject: Re: Deleting incoming network packets / sk_buff
Date: Sun, 15 Aug 2004 11:18:42 -0700 [thread overview]
Message-ID: <411FA902.8070402@candelatech.com> (raw)
In-Reply-To: <411FA5D0.6000004@web.de>
Michael Renzmann wrote:
> Bottom line: the easiest way to solve this problem would be to have some
> way for blocking packets on eth1 from being processed (after they have
> been passed to the packet socket - else my userspace program won't be
> able to "bridge" incoming packets to tap0).
Can't you have no IP on eth1 and have your IP on tap0 instead? That would
at least keep any pkts received on eth1 from being processed by the
IP stack.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2004-08-15 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 19:12 Deleting incoming network packets / sk_buff Michael Renzmann
2004-08-14 22:15 ` Ben Greear
2004-08-15 18:05 ` Michael Renzmann
2004-08-15 18:18 ` Ben Greear [this message]
2004-08-15 18:57 ` Michael Renzmann
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=411FA902.8070402@candelatech.com \
--to=greearb@candelatech.com \
--cc=mrenzmann@web.de \
--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).