On my home network, I have IPv6 configured to use SLAAC, and I sometimes end up with devices with many addresses in the deprecated state. I'm guessing this is due to privacy extensions causing the address to rotate periodically. We still advertise these addresses in callmemaybe and send disco pings to them, and they're reported up to control. I think they probably shouldn't be; the intent of the deprecated status is that the address is only still around for existing connections but shouldn't be used for new ones. The tradeoff is obviously that these addresses then wouldn't be available as possible connectivity candidates, but it's probably worth eating that marginal cost for more sensible behavior. Todo here is to see what if anything the go codebase does about this.
Anyway, regardless of what we do in the runtime about it, the first thing to do is just to track the flag in netmon.
On my home network, I have IPv6 configured to use SLAAC, and I sometimes end up with devices with many addresses in the deprecated state. I'm guessing this is due to privacy extensions causing the address to rotate periodically. We still advertise these addresses in callmemaybe and send disco pings to them, and they're reported up to control. I think they probably shouldn't be; the intent of the deprecated status is that the address is only still around for existing connections but shouldn't be used for new ones. The tradeoff is obviously that these addresses then wouldn't be available as possible connectivity candidates, but it's probably worth eating that marginal cost for more sensible behavior. Todo here is to see what if anything the go codebase does about this.
Anyway, regardless of what we do in the runtime about it, the first thing to do is just to track the flag in netmon.