From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Alpt <alpt@freaknet.org>
Cc: netfilter@lists.netfilter.org, linux-net@vger.kernel.org
Subject: Re: Different routes for different src addresses
Date: Wed, 07 Jul 2004 10:38:41 -0400 [thread overview]
Message-ID: <1089211121.21756.6.camel@localhost> (raw)
In-Reply-To: <20040707120502.GA23120@nihil>
On Wed, 2004-07-07 at 08:05, Alpt wrote:
> Hi all,
> is it possible to create a route for a single src address?
> For example these are some routes I'd like to use:
>
> 1) "All the pkts coming from hostA with dst=hostX are routed to eth1".
> 2) "All the pkts coming from hostB with dst=hostT are routed to eth0"
> /*Normal routes start here*/
> 3) "All the pkts (that are not pkts of type 1) and 2)) with dst=hostX
> are routed to eth3"
> 4) "All the pkts (that are not pkts of type 1) and 2)) with dst=hostU
> are routed to eth2"
> 5) And so on...
>
>
> I mean _routing_, not natting. If I nat the pkts their destination will
> change and I need to keep it intact.
>
> In the FIB routing table I can only specify the target address, but I've
> noticed that the kernel's cache matches the source field. But when I try
> to modify it I get: "Modifying `inet' routing cache not supported".
> So, Is it possible to modify the krnl's cache from the user space with
> some magic ioctl?
>
> Is there a solution for this problem? Can netfilter do something for
> this?
>
> And, what's the best method to modify the FIB from user space? The ioctl
> or the rtnetlink?
>
> Thank you (^_^)
> I live waiting your wise reply
I have not digested your question fully but my initial reaction is that
it can be done with iproute2. If you are unfamiliar with it, look for a
file named ip-cref.ps in your distribution. In RedHat, it is typically
under /usr/share/doc/iproute-2.4.7/ - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
prev parent reply other threads:[~2004-07-07 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 12:05 Different routes for different src addresses Alpt
2004-07-07 12:39 ` Martijn van Oosterhout
2004-07-07 13:10 ` Antony Stone
2004-07-07 21:02 ` Nick Taylor
2004-07-07 21:36 ` Antony Stone
2004-07-08 5:52 ` Alpt
2004-07-07 14:38 ` John A. Sullivan III [this message]
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=1089211121.21756.6.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=alpt@freaknet.org \
--cc=linux-net@vger.kernel.org \
--cc=netfilter@lists.netfilter.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 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.