netdev - Re: [RFC] Allow ipv6 proxies and arp proxies be shown with ip

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]

Date:	Wed, 25 Jan 2012 21:40:08 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	kuznet@....inr.ac.ru
Cc:	antonz@...allels.com, ynot@...natka.ru, netdev@...r.kernel.org,
	xemul@...allels.com
Subject: Re: [RFC] Allow ipv6 proxies and arp proxies be shown with ip

From: Alexey Kuznetsov <kuznet@....inr.ac.ru>
Date: Thu, 26 Jan 2012 02:59:31 +0400

> I see two variants:
> 
> 1. On request to list proxy entries, ip utility could send request containing
>    full ndmsg with NTF_PROXY set in ndm_flags. When kernel sees request without NTF_PROXY,
>    it dumps normal neighbor table. When it sees NTF_PROXY, it dumps proxy table instead.
> 
>    From user viewpoint, "ip neigh list ..." works as usual, "ip neigh list proxy ..." will list
>    proxy entries.
> 
> 2. Adding RTM_*PNEIGH and the whole new set of "ip pneigh ..." commands.
>    Logically, I would prefer this solution and, unless I was lazy 10 years ago, I would
>    go this way. Unfortunately, this will break compatibility with existing
>    "ip neigh add/del proxy ...", so that the kludge to intercept NTF_PROXY command in RTM_*NEIGH
>    is still required and the solution loses half of its beauty.
> 
> So, seems #1 looks better.

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