On 12/26/2019 02:05 AM, Jouni Malinen wrote:
On Mon, Mar 18, 2019 at 01:46:34PM -0700, greearb@xxxxxxxxxxxxxxx wrote:
Let users delete a neighbor by BSSID alone if they prefer.
The underlying code already properly handled a null SSID, so
just relax the CLI calling restrictions.
Thanks, applied.
And, if user tries to delete a neigh entry that is already deleted,
return OK instead of failure.
But I dropped this part since it seems to be completely separate item
from the main change and would change the existing interface in a manner
that does not seem to be necessary and may be unexpected and
furthermore, it breaks the rrm_neighbor_db test case.
Would you consider a version of this patch that took an extra 'force'
or similar argument? While automating this, we would rather the
delete not fail if the target is already gone: The system is already in
the desired state, so automation should not need to deal with any
extra fault recovery in this state.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
