From: Alexey Kuznetsov <redacted>
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.