From 19d64edf74bd5f7f0aceb356f5855ed5bdad48f4 Mon Sep 17 00:00:00 2001 From: YOSHIFUJI Hideaki Date: Wed, 23 Aug 2006 17:23:39 -0700 Subject: [PATCH] --- yaml --- r: 34554 b: refs/heads/master c: 4e96c2b4180aff4f080b77314712073c6ca430e7 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/net/ipv6/Kconfig | 14 ++++++++++++++ 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index 29487394b28c..b45739a0976c 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: c0bece9f2aec546c3750ae3972f80e024a923f34 +refs/heads/master: 4e96c2b4180aff4f080b77314712073c6ca430e7 diff --git a/trunk/net/ipv6/Kconfig b/trunk/net/ipv6/Kconfig index 36a6c2b79889..14f0b336519f 100644 --- a/trunk/net/ipv6/Kconfig +++ b/trunk/net/ipv6/Kconfig @@ -136,6 +136,20 @@ config IPV6_TUNNEL If unsure, say N. +config IPV6_SUBTREES + bool "IPv6: source address based routing" + depends on IPV6 && EXPERIMENTAL + ---help--- + Enable routing by source address or prefix. + + The destination address is still the primary routing key, so mixing + normal and source prefix specific routes in the same routing table + may sometimes lead to unintended routing behavior. This can be + avoided by defining different routing tables for the normal and + source prefix specific routes. + + If unsure, say N. + config IPV6_MULTIPLE_TABLES bool "IPv6: Multiple Routing Tables" depends on IPV6 && EXPERIMENTAL