From: "Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: ML netfilter <netfilter@vger.kernel.org>
Subject: Re: IPTables : How to force data coming from ethX being output by the same device
Date: Wed, 23 Apr 2008 12:38:00 -0300 [thread overview]
Message-ID: <480F57D8.1060704@solutti.com.br> (raw)
In-Reply-To: <alpine.LNX.1.10.0804231717190.13697@fbirervta.pbzchgretzou.qr>
Jan Engelhardt escreveu:
>
> It is not completely not related. By changing things such as
> nfmark, TOS field, source or destination address, routing can
> be influenced, so I would not say it's totally unrelated :)
>
Changing all these parameters will do nothing if you dont have
appropriate routing rules that uses them as routing criteria parameters.
Well .... yes, it's not completly unrelated, iptables really can
'help' routing decisions with those things.
iptables can be used to help routing decisions, but this is not the
only way of doing it. You can have your source routing rules and get
advanced routing without iptables rules, it's not required, but yes can
be used sometimes. On pretty advanced routing situations, maybe iptables
'helping' rules would be necessary, but advanced routing can be done
without iptables.
--
Atenciosamente / Sincerily,
Leonardo Rodrigues
Solutti Tecnologia
http://www.solutti.com.br
Minha armadilha de SPAM, NÃO mandem email
gertrudes@solutti.com.br
My SPAMTRAP, do not email it
next prev parent reply other threads:[~2008-04-23 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 14:03 IPTables : How to force data coming from ethX being output by the same device Yves DUF
2008-04-23 14:37 ` Leonardo Rodrigues Magalhães
2008-04-23 14:42 ` Jan Engelhardt
2008-04-23 14:51 ` Leonardo Rodrigues Magalhães
2008-04-23 15:17 ` Jan Engelhardt
2008-04-23 15:21 ` John covici
2008-04-23 16:12 ` Jan Engelhardt
2008-04-23 15:38 ` Leonardo Rodrigues Magalhães [this message]
2008-04-23 16:33 ` Alexei Ustyuzhaninov
2008-04-23 17:31 ` Leonardo Rodrigues Magalhães
2008-04-23 18:50 ` Jan Engelhardt
2008-04-24 4:38 ` Alexei Ustyuzhaninov
2008-04-23 14:49 ` Leonid Zeitlin
2008-04-23 19:06 ` Yves DUF
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=480F57D8.1060704@solutti.com.br \
--to=leolistas@solutti.com.br \
--cc=jengelh@computergmbh.de \
--cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox