On Thu, Dec 26, 2019 at 09:14:22AM -0800, Ben Greear wrote: > I can check the code again when I get a chance, but from what I recall, > it was not convenient to make sure we removed entries exactly once in > all cases, so our code ended up doing duplicated removes in some cases. > It was easier to make hostap ignore the duplicate removes instead > of parsing errors to figure out if the error was related to removing > a non-existing entity or not. You don't need to remove the entries exactly once; you'd need to simply ignore the response value (FAIL or OK).. If you want to remove all added entries, it would be simpler to add "REMOVE_NEIGHBOR *" which would remove all neighbor DB entries except for the automatically added local entry and return "OK" regardless of whether entries were removed. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
