netdev - [ndisc6] Bad NIC causing IPV6 NDP to stop working

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: <D8C50530D6022F40A817A35C40CC06A70B34C74BF3@DUBX7MCDUB01.EMEA.DELL.COM>
Date:	Wed, 20 Jun 2012 18:09:39 +0100
From:	<Menny_Hamburger@...l.com>
To:	<netdev@...r.kernel.org>
Subject: [ndisc6] Bad NIC causing  IPV6 NDP to stop working

Hi,

We have witnessed several cases where we suspect that a bad NIC on the machine caused neighbour discovery to stop working on all the other NICs - when this happens ping6 fails on every NIC we try it.
>From looking into the code I see that there is only a single socket assigned for NDP; Does it sound logical to allocate a socket per interface instead of a single global socket.

Thanks,
Menny

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