Re: bin/57957: dhcpcd fails to unconfigure addresses from released lease

[Roy Marples <roy%marples.name@localhost>]

 ---- On Sun, 25 Feb 2024 20:00:03 +0000  Taylor R Campbell  wrote --- 
 > The following reply was made to PR bin/57957; it has been noted by GNATS.
 > 
 > From: Taylor R Campbell riastradh%NetBSD.org@localhost>
 > To: Roy Marples roy%marples.name@localhost>
 > Cc: "Robert Elz" kre%munnari.OZ.AU@localhost>,
 >     gnats-bugs%NetBSD.org@localhost,
 >     gnats-admin%NetBSD.org@localhost,
 >     netbsd-bugs%NetBSD.org@localhost
 > Subject: Re: bin/57957: dhcpcd fails to unconfigure addresses from released
 >     lease
 > Date: Sun, 25 Feb 2024 19:58:54 +0000
 > 
 >  > Date: Sun, 25 Feb 2024 16:31:10 +0000
 >  > From: Roy Marples roy%marples.name@localhost>
 >  > 
 >  > No-one has posted yet what their expected address lifetimes are and
 >  > what they see from ifconfig.
 >  
 >  The main point of this PR is that even after I asked dhcpcd to release
 >  _everything_ with `dhcpcd -k' (no interface argument, because of
 >  https://gnats.NetBSD.org/57956), it deleted all addresses _except_ for
 >  the old DHCPv6 addresses.

That is because it's no longer part of the active lease.
dhcpcd now tracks every address, so it should be easy to remove any address that was added from a lease but no longer part of one.
This won't survive dhcpcd being restarted, but that should be fine yes?

 >  (Now, another issue is why did the system continue to use the old
 >  address as a source address, losing my IPv6 connectivity?  Also to be
 >  investigated, and perhaps related -- perhaps dhcpcd forgot about it
 >  and treated it as a manually configured address and somehow that led
 >  to its being the default source address -- but let's keep this PR
 >  focussed on how `dhcpcd -k' failed to unconfigure addresses it had
 >  previously configured.)

Sure

Roy