Jana Radhakrishnan 2ba6c399ea Ensure purging neighbor cache for stale deletes ... 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>		2016-09-07 10:45:40 -07:00
..
ovmanager	ovmanager: Error out on vxlan id alloc failure	2016-06-28 13:46:22 -07:00
encryption.go	Merge pull request #1356 from aboch/isb	2016-07-25 19:16:01 -07:00
filter.go	Overlay driver to check for chain presence	2016-04-13 10:47:42 -07:00
joinleave.go	Merge pull request #1337 from mavenugo/adv-addr	2016-07-21 09:51:51 -07:00
ov_endpoint.go	Persist and restore overlay endpoints to handle daemon restart	2016-06-13 23:48:00 -07:00
ov_network.go	Propage the vxlan device creation error in driver to libnetwork	2016-08-21 15:52:40 -07:00
ov_serf.go	Adding Advertise-addr support	2016-07-21 02:44:25 -07:00
ov_utils.go	Allow user to set the overlay network's mtu	2016-07-23 22:39:29 -07:00
overlay.go	Allow reattempt of overlay network sbox join	2016-08-01 08:08:51 -07:00
overlay.pb.go	Convert overlay peer updates to use protobuf	2016-05-18 20:44:50 -07:00
overlay.proto	Convert overlay peer updates to use protobuf	2016-05-18 20:44:50 -07:00
overlay_test.go	Add libnetwork agent mode support	2016-05-02 18:19:32 -07:00
peerdb.go	Ensure purging neighbor cache for stale deletes	2016-09-07 10:45:40 -07:00