From: "Adrian Moreno" <adrian_linux@gmx.com>
To: lartc@vger.kernel.org
Subject: Fw: IPv6 Dynamic gateways in separate routing tables
Date: Wed, 09 Oct 2013 13:20:37 +0000 [thread overview]
Message-ID: <20131009132038.302570@gmx.com> (raw)
Hi all,
I have a multihomed system (very similar to the one described in LARTC HowTo Section 4.2. Routing for multiple uplinks/providers) with IPv6 addresses.
I want to create a routing table per interface to be able to route the traffic depending on the source address using IPv6 addresses and dynamic gateways.
How do I set the default gateway to be dynamic in a separate routing table?
My current configuration is:
IF_1: Interface 1
SUBNET_1: the subnet connected to Interface 1
IPv6_1: IPv6 address configured on Interface 1
T_1: Routing table for Interface 1
IF_2: Interface 2
SUBNET_2: the subnet connected to Interface 2
IPv6_2: IPv6 address configured on Interface 2
T_2: Routing table for Interface 2
Configuration:
ip -6 route add $SUBNET_1 dev $IF_1 table $T_1
ip -6 rule add from $IPv6_1 table $T_1
I am clearly missing one route, that should look like:
ip -6 route add default via <GATEWAY_1> tab $T_1
How should I set this route to use the dynamically obtained gateway?
The dynamic gateways are listed in the "default" routing table as:
% ip -6 route show default
default via DYNAMIC_GWv6_1 dev IF_1 proto kernel metric ....
default via DYNAMIC_GWv6_2 dev IF_2 proto kernel metric ....
The order in which these routes are listed is arbitrary (restarting /etc/init.d/networking re-shuffles them).
Is there a way to ensure that a packet being sent from IPv6_1 goes out via the correct gateway (DYNAMIC_GWv6_1) and interface (IF_1)?
Many thanks in advance for any help.
Adrian
next reply other threads:[~2013-10-09 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 13:20 Adrian Moreno [this message]
2013-10-09 14:12 ` IPv6 Dynamic gateways in separate routing tables Remy Mudingay
2013-10-09 14:37 ` Adrian Moreno
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=20131009132038.302570@gmx.com \
--to=adrian_linux@gmx.com \
--cc=lartc@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 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.