Ah, the observed address data as input to address allocation is cool.
But still - an address that has not been seen for a week and does not
respond to a ping or other detection should surely be deletable?
Perhaps there should be a customisable threshold (say, 1 week by
default) for auto-scrubbing. At that point, the address is hard-probed
to see if it is responsive in a way that might cause problems, and if
not, then the record can safely be removed altogether.
Separately, I do think the user should be able to trigger a one-time
iteration of that scrub with a custom threshold ("scrub addresses that
have not been seen in n days/hours").
Ah, the observed address data as input to address allocation is cool.
But still - an address that has not been seen for a week and does not
respond to a ping or other detection should surely be deletable?
Perhaps there should be a customisable threshold (say, 1 week by
default) for auto-scrubbing. At that point, the address is hard-probed
to see if it is responsive in a way that might cause problems, and if
not, then the record can safely be removed altogether.
Separately, I do think the user should be able to trigger a one-time
iteration of that scrub with a custom threshold ("scrub addresses that
have not been seen in n days/hours").
Mark