netdev - CONFIG_ARPD help text

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

Message-ID: <4A314CC5.9090505@iki.fi>
Date:	Thu, 11 Jun 2009 21:28:21 +0300
From:	Timo Teräs <timo.teras@....fi>
To:	netdev@...r.kernel.org
Subject: CONFIG_ARPD help text

Hi,

I just re-read again the CONFIG_ARPD help text. It says it's
"experimental and also obsolete".

But as opennhrp relies on this, and has shown the usefulness for
this interface - it can be used to implement other protocols that
resolve neighbor address than ARP in userland. In this case the
NHRP protocol.

Would it be acceptable to remove the designation as "obsolete"?

Also, I'm running the opennhrp on production with reasonable
size network (100+ nodes in gre subnet). And with the fix I sent
previously it seems to work very stable. Is there something more
to be done, or could the "experimental" marking be removed also?

I could also update the help to explain where the option is useful.
Or should the option be renamed to something like NEIGH_NETLINK?
It also seems that IPv6 supports CONFIG_ARPD so it should probably
be moved from net/ipv4/Kconfig to likely net/core/Kconfig?

Thanks,
  Timo
--
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