From: Patrick McHardy <kaber@trash.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev@vger.kernel.org, vnuorval@tcs.hut.fi,
usagi-core@linux-ipv6.org, yoshfuji@linux-ipv6.org,
davem@davemloft.net, anttit@tcs.hut.fi
Subject: Re: [PATCH 2/5] [IPV6]: Multiple Routing Tables
Date: Sat, 05 Aug 2006 11:00:36 +0200 [thread overview]
Message-ID: <44D45E34.9030607@trash.net> (raw)
In-Reply-To: <20060804102636.322297243@postel.suug.ch>
[-- Attachment #1: Type: text/plain, Size: 641 bytes --]
Thomas Graf wrote:
> Index: net-2.6.19/net/ipv6/route.c
> ===================================================================
> --- net-2.6.19.orig/net/ipv6/route.c
> +++ net-2.6.19/net/ipv6/route.c
> @@ -1750,6 +1843,10 @@ static int rt6_fill_node(struct sk_buff
> rtm->rtm_dst_len = rt->rt6i_dst.plen;
> rtm->rtm_src_len = rt->rt6i_src.plen;
> rtm->rtm_tos = 0;
> + if (rt->rt6i_table)
> + rtm->rtm_table = rt->rt6i_table->tb6_id;
> + else
> + rtm->rtm_table = RT6_TABLE_UNSPEC;
> rtm->rtm_table = RT_TABLE_MAIN;
This looks like a mistake, the table ID is overwritten again.
Signed-off-by: Patrick McHardy <kaber@trash.net>
[-- Attachment #2: x --]
[-- Type: text/plain, Size: 443 bytes --]
diff --git a/net/ipv6/route.c b/net/ipv6/route.c
index d5c39c4..3ea6db9 100644
--- a/net/ipv6/route.c
+++ b/net/ipv6/route.c
@@ -1898,7 +1898,6 @@ static int rt6_fill_node(struct sk_buff
rtm->rtm_table = rt->rt6i_table->tb6_id;
else
rtm->rtm_table = RT6_TABLE_UNSPEC;
- rtm->rtm_table = RT_TABLE_MAIN;
if (rt->rt6i_flags&RTF_REJECT)
rtm->rtm_type = RTN_UNREACHABLE;
else if (rt->rt6i_dev && (rt->rt6i_dev->flags&IFF_LOOPBACK))
next prev parent reply other threads:[~2006-08-05 9:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 10:23 [PATCHSET] Multiple IPV6 Routing Tables & Policy Routing Thomas Graf
2006-08-03 22:00 ` [PATCH 1/5] [IPV6]: Remove ndiscs rt6_lock dependency Thomas Graf
2006-08-03 22:00 ` [PATCH 2/5] [IPV6]: Multiple Routing Tables Thomas Graf
2006-08-05 9:00 ` Patrick McHardy [this message]
2006-08-05 9:21 ` David Miller
2006-08-03 22:00 ` [PATCH 3/5] [NET]: Protocol Independant Policy Routing Rules Framework Thomas Graf
2006-08-03 22:00 ` [PATCH 4/5] [IPV6]: Policy Routing Rules Thomas Graf
2006-08-03 22:00 ` [PATCH 5/5] [IPV4]: Use Protocol Independant Policy Routing Rules Framework Thomas Graf
2006-08-04 10:40 ` [PATCHSET] Multiple IPV6 Routing Tables & Policy Routing David Miller
2006-08-04 15:58 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-04 17:41 ` Thomas Graf
2006-08-04 18:14 ` YOSHIFUJI Hideaki / 吉藤英明
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 22:11 [RFC] " Thomas Graf
2006-07-26 22:00 ` [PATCH 2/5] [IPV6]: Multiple Routing Tables Thomas Graf
2006-07-26 22:39 ` David Miller
2006-07-26 22:48 ` Thomas Graf
2006-07-26 22:55 ` David Miller
2006-07-29 4:13 ` YOSHIFUJI Hideaki / 吉藤英明
2006-07-29 4:14 ` David Miller
2006-07-29 4:28 ` YOSHIFUJI Hideaki / 吉藤英明
2006-07-29 10:29 ` Thomas Graf
2006-07-31 13:55 ` Ville Nuorvala
2006-07-31 14:01 ` Herbert Xu
2006-07-31 14:02 ` Herbert Xu
2006-07-31 15:41 ` Thomas Graf
2006-07-31 20:09 ` David Miller
2006-07-31 15:34 ` Thomas Graf
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=44D45E34.9030607@trash.net \
--to=kaber@trash.net \
--cc=anttit@tcs.hut.fi \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=usagi-core@linux-ipv6.org \
--cc=vnuorval@tcs.hut.fi \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).