From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: multiple routing tables for internal router programs
Date: Mon, 11 Jun 2007 10:58:28 -0500 [thread overview]
Message-ID: <466D7124.9090107@riverviewtech.net> (raw)
In-Reply-To: <466D5F4E.3010605@gmail.com>
On 06/11/07 09:42, Andrea wrote:
> But how can I reach the same result for programs that are working
> INTO the linux box? All I want is that a program (ping, for examples,
> or a VOIP server, better) uses a secondary routing table in the same
> machine. In this mode, I can manipulate route settings for different
> classes of program in my router.
Just like you are using IPTables to mark packets now and then based
routing decisions based on the IPTables mark, mark packets inbound as
you want to.
There is no limit on the number of ways that you can mark packets,
inbound, outbound, source port, destination port, what ever.
(That is if I have understood you correctly.)
Grant. . . .
prev parent reply other threads:[~2007-06-11 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 14:42 multiple routing tables for internal router programs Andrea
2007-06-11 15:58 ` Grant Taylor [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=466D7124.9090107@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=gtaylor+reply@riverviewtech.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox