netdev - Re: [PATCH v2] neigh: set nud_state to NUD_INCOMPLETE when probing router reachability

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

Date:	Tue, 13 May 2014 09:39:31 -0700
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Duan Jiong <duanj.fnst@...fujitsu.com>,
	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, jbenc@...hat.com
Subject: Re: [PATCH v2] neigh: set nud_state to NUD_INCOMPLETE when probing
 router reachability

On Mon, May 12, 2014, at 22:12, Duan Jiong wrote:
> In situation of connected router, the router which enter NUD_FAILED will
> never be choosed, and we only probe NUD_FAILED router's reachability by
> sending
> a single Neighbor Solicitation to that router's address.  Finally， we 
> still send packets out through the connected router.

I agree with the patch mostly. The reason why I would liked to see
another change without changing nud_state is that we export those states
to user space.

Greetings,

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