From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: iptables + ROUTE
Date: Thu, 09 Nov 2006 11:11:33 +0100 [thread overview]
Message-ID: <4552FED5.8070701@plouf.fr.eu.org> (raw)
In-Reply-To: <20061109054042.267180@gmx.net>
Hello,
Mato Vidovic a écrit :
>
> I have a need to perform TOS based traffic routing.
> That means I have two interfaces (say eth0 and eth1) to backbone
> and I need to route the real-time critical
> IP traffic over eth1 and the remaining IP traffic over eth0.
> After a lot of experimenting I came to the conclusion that something
> like the following would do:
>
> # iptables -t mangle -A POSTROUTING -m tos --tos 16 -j ROUTE --oif eth1
> # iptables -t mangle -A POSTROUTING -m tos --tos !16 -j ROUTE --oif eth0
Why not just use the TOS selection feature in advanced routing
(involving routing rules and alternate routing tables) ?
Something like :
ip rule add tos 16 lookup tos16 priority 100
ip route add default dev eth1 table tos16
> Unfortunately the Linux box says:
> "No chain/target/match by that name"
>
> The kernel I use is 2.6.18, iptables version is the last debian
> stable version 1.2.11.
>
> Any idea what is wrong here (am I missing something in the
> configuration, or a library, or am I completely wrong maybe...)?
As Edvin Seferovic wrote, the kernel part of the ROUTE target is not
included in the mainstream kernel yet. You can add it to your kernel
source tree with the patch-o-matic-ng a build a ROUTE-capable kernel.
next prev parent reply other threads:[~2006-11-09 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 5:40 iptables + ROUTE Mato Vidovic
2006-11-09 6:44 ` Seferovic Edvin
2006-11-09 10:11 ` Pascal Hambourg [this message]
[not found] <001301c4f465$2ae966b0$030aa8c0@T>
2005-01-10 10:07 ` iptables ROUTE Cedric de Launois
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=4552FED5.8070701@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.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.