netdev - Multiple default router probe in Linux 3.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAGgZr_3w4wb-LGJ61iTj2ishtnno=m7jOs0o8PqwmZNwt9Bjmg@mail.gmail.com>
Date:	Thu, 9 Apr 2015 00:54:02 +0800
From:	Xin Huang <huangxin811@...il.com>
To:	netdev@...r.kernel.org
Subject: Multiple default router probe in Linux 3.14

Hi, guys,

I'm trying to pass IPv6 ready logo test for my project and have
question on Linux multiple default router probe implementation.
Router may have multiple default router in its list if multiple RA
received, all have same priority set.
When router send NS to 1st router but do not get NA response, it
should send NS to 2nd router to check if it's reachable. This feature
seems covered by implementation of option CONFIG_IPV6_ROUTER_PREF, but
only effect when net->ipv6.devconf_all->forwarding is disabled(that
means host mode).
But in the case that router's life time is still valid but it's
reachable expired, the default router is not removed from router table
and we are still in router mode, we should also probe second router if
first router do not respond NS, I need probe logic taking effect in
this mode(net->ipv6.devconf_all->forwarding is 1). It seems conflict
with current Linux implementation.
Can we remove 'net->ipv6.devconf_all->forwarding' check when call
rt6_check_neigh()? Or any other suggestion?

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html