netdev - Re: PROBLEM: Linux 3.9 more-specific ipv6 route ignored until next-hop is in neighbor cache

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+PSOpziMTBD-dNbjtYO+EcvoMuO0NBw7V-0OHCtAAzZQEG4Uw@mail.gmail.com>
Date:	Thu, 4 Jul 2013 07:20:37 +0200
From:	Pierre Emeriaud <petrus.lt@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	hannes@...essinduktion.org,
	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
	netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org
Subject: Re: PROBLEM: Linux 3.9 more-specific ipv6 route ignored until
 next-hop is in neighbor cache

2013/7/4 David Miller <davem@...emloft.net>:
>>
>> [PATCH net v2] ipv6: rt6_check_neigh should successfully verify neigh if no NUD information are available
>
> Applied and queued up for -stable, thanks everyone.

I just tested the patch and it works fine! The more-specific route is
now preferred over default even if the next-hop is not (yet) known in
the neighbor cache.

Thanks everyone !

-pierre.
--
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