From: Andrea <andang76@gmail.com>
To: netfilter@lists.netfilter.org
Subject: multiple routing tables for internal router programs
Date: Mon, 11 Jun 2007 16:42:22 +0200 [thread overview]
Message-ID: <466D5F4E.3010605@gmail.com> (raw)
Maybe a strange request, I'll try to explain this as clearer as I can
(forgive my bad english, please :-) ).
I'm setting a linux box as a router. My router uses multiple routing
tables, so I can address the traffic from specific ip addresses of my
lan to distinct ISPs providers (specifying a different default gateway
fo r each table), marking packets with iptables (prerouting marks).
This works with the forwarding traffic (lan-ISPs) that crosses my router.
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.
Is it possible?
Thanks
next reply other threads:[~2007-06-11 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 14:42 Andrea [this message]
2007-06-11 15:58 ` multiple routing tables for internal router programs Grant Taylor
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=466D5F4E.3010605@gmail.com \
--to=andang76@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox