From: Daniel Chemko <dchemko@smgtec.com>
To: Bruce Henshaw <salacious@redphive.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: ROUTE extension for linux 2.6.3 HELP
Date: Sun, 07 Mar 2004 01:57:20 -0800 [thread overview]
Message-ID: <404AF200.60200@smgtec.com> (raw)
In-Reply-To: <1078615714.12327.10.camel@localhost>
You don't need the route extension to do "policy routing". All you need
is CONNMARK, and a customized iproute2 setup that has multiple routes
set up.
Pseudo-tasks:
Add routing tables for each WAN interface
Add routing rules that link FWMARK's with the routing tables previously
created.
Add CONNMARK and MARK entries to PREROUTING and/or OUTPUT in order to
keep track of sessions and direct traffic to the routing table you
desire by setting the packet's firewall MARK.
Profit!
If you've exhausted researching what I have described above, come back
and I'll give some more detail. I am pretty tired at this point, so I
wouldn't be much help (2:00 am)..
Bruce Henshaw wrote:
>Hello,
>
> I have a need to direct certain traffic out certain WAN interfaces,
>which have dynamic addresses.
>
> I'm unable to patch my 2.6.3 kernel with the ROUTE extension though. :(
>is there another way to do that?
>
>I tried the new patch-o-matic-ng CVS and it says ROUTE requires kernel <
>2.6.0
>
> But I do see this file.
>
> patch-o-matic-ng/ROUTE/linux-2.6/net/ipv4/netfilter/ipt_ROUTE.c
>
> How I can add ROUTE in my 2.6.3 kernel?
>
> Thanks very much for reading about my problem.
>
>Bruce Henshaw
>
>
>
>
prev parent reply other threads:[~2004-03-07 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-06 23:28 ROUTE extension for linux 2.6.3 HELP Bruce Henshaw
2004-03-07 9:57 ` Daniel Chemko [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=404AF200.60200@smgtec.com \
--to=dchemko@smgtec.com \
--cc=netfilter@lists.netfilter.org \
--cc=salacious@redphive.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.