From: "François Delawarde" <fdelawarde@wirelessmundi.com>
To: netfilter@lists.netfilter.org
Subject: Re-routing of output traffic
Date: Wed, 20 Jun 2007 14:06:37 +0200 [thread overview]
Message-ID: <4679184D.5090808@wirelessmundi.com> (raw)
Hello all!
If i'm not wrong, outgoing traffic generated by local processes pass
through the following:
Local Process ==> OUTPUT [mangle] ==> OUTPUT [nat] ==> Rerouting ==>
OUTPUT [filter] ==> POSTROUTING ...
I'm interested in using a specific routing table for one of my local
processes (the entire story is complicated).
I tried the following without success:
iptables -t mangle -A OUTPUT -m owner --gid-owner <group of process> -j
MARK --set-mark <mark value>
ip rule add prio 1 fwmark <mark value> table 12
ip route add default via 192.168.1.1 table 12
But doing the following, it works perfectly:
iptables -t mangle -A OUTPUT -m owner --gid-owner <group of process> -j
TOS --set-tos <tos value>
ip rule add prio 1 tos <tos value> table 12
ip route add default via 192.168.1.1 table 12
I had read that MARKing a paquet could trigger the "Rerouting" part, but
it appears that in the real world, the "Rerouting" part takes place only
when we actually change something in the packet like TOSing it or
DNATing it.
Is this a bug, or is it supposed to work that way? Is there anyway of
doing what I want using MARKs (and without having to use the ROUTE target)?
I'm using iptables 1.3.7 with unpatched debian etch kernel 2.6.18-4.
Thank you,
François.
next reply other threads:[~2007-06-20 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 12:06 François Delawarde [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-20 12:08 Re-routing of output traffic François Delawarde
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=4679184D.5090808@wirelessmundi.com \
--to=fdelawarde@wirelessmundi.com \
--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.