From: "John A. Sullivan III" <jsullivan@opensourcedevelopmentcorp.com>
To: Scott MacKay <scottmackay@yahoo.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Altering destination ethernet device
Date: Fri, 25 Jun 2004 10:03:59 -0400 [thread overview]
Message-ID: <1088172238.30481.16.camel@localhost> (raw)
In-Reply-To: <20040625130142.54545.qmail@web13907.mail.yahoo.com>
On Fri, 2004-06-25 at 09:01, Scott MacKay wrote:
> Hello,
> Sorry if this was asked before by someone, but is
> it possible to alter the destination interface for a
> packet? In example, if I have a packet coming in eth0
> which could go out either eth1 or eth2, is there any
> way to force it to eth2? I would be looking for a
> programming solution because the actual interface
> selected will be based on some critea which is
> programmed. If it is possible, I would likely select
> the new interface in mangle/POSTROUTING unless it
> needed to be elsewhere.
<snip>
This may be better suited to iproute2. To read the documentation, look
for a file named ip-cref.ps in your distribution. There is a brief
slide show on using it in the training section at
http://iscs.sourceforge.net but it is directed towards using it with
FreeS/WAN. I do not know what APIs are available. - John
--
Open Source Development Corporation
Financially sustainable open source development
http://www.opensourcedevelopmentcorp.com
next prev parent reply other threads:[~2004-06-25 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 10:27 pom-ng include question Eicke Friedrich
2004-06-25 11:07 ` Jozsef Kadlecsik
2004-06-25 11:16 ` Kernel 2.6 conntrack defragment of IP packets Scott MacKay
2004-06-25 13:01 ` Altering destination ethernet device Scott MacKay
2004-06-25 14:03 ` John A. Sullivan III [this message]
2004-06-25 14:16 ` Scott MacKay
2004-06-25 14:39 ` Henrik Nordstrom
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=1088172238.30481.16.camel@localhost \
--to=jsullivan@opensourcedevelopmentcorp.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=scottmackay@yahoo.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.