2ba6c399ea
When stale delete notifications are received, we still need to make sure to purge sandbox neighbor cache because these stale deletes are most typically out of order delete notifications and if an add for the peermac was received before the delete of the old peermac,vtep pair then we process that and replace the kernel state but the old neighbor state in the sandbox cache remains. That needs to be purged when we finally get the out of order delete notification. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com> |
||
|---|---|---|
| .. | ||
| interface_freebsd.go | ||
| interface_linux.go | ||
| interface_solaris.go | ||
| interface_windows.go | ||
| namespace_linux.go | ||
| namespace_unsupported.go | ||
| namespace_windows.go | ||
| neigh_freebsd.go | ||
| neigh_linux.go | ||
| neigh_solaris.go | ||
| neigh_windows.go | ||
| options_linux.go | ||
| route_linux.go | ||
| sandbox.go | ||
| sandbox_freebsd.go | ||
| sandbox_linux_test.go | ||
| sandbox_test.go | ||
| sandbox_unsupported.go | ||
| sandbox_unsupported_test.go | ||