Cisco Bug: CSCtd82463 - dhcpv6 leaseqeury acquires client, does not check if it has desired lease
Nov 29, 2016
- Cisco Network Registrar
Known Affected Releases
7.0 7.1 7.2
Symptom: In some situations, a DHCPv6 Leasequery response may be presented as a successful response to a IPv6 based leasequery, when in fact the IPv6 address that was the subject of the query does not actually appear in the response. Conditions: This very rare situation could only occur if the IPv6 address was leased to a DHCPv6 client when the DHCPv6 leasequery arrived at the DHCP server for processing, but then while the leasequery was awaiting access to the DHCPv6 client to be processed the DHCPv6 client in question became disassociated from that lease. Then, when the DHCPv6 leasequery gained access to that DHCPv6 client, the lease would not be there (and the problem is that there is no check for this very rare situation). This was discovered by code inspection, and may well never have happened in reality.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases