Infoblox uses the ISC DHCP code. I'm thin on details.
> 1) What's the pattern with which addresses are generated/assigned? Are
> they sequential (fc00::1, fc00::2, etc.)? Random? Something else?
The manual says "When the server grants IPv6 leases, it uses an
algorithm based on the DUID of the c
Fernando
Wrt to the Cisco DHCPv6 server (CNR):
1) sequential or random per configuration (can send multiple IA_NA/IA_TA
if there are multiple prefixes configured for this link)
2) while client can send a 'hint' to re-use previous addresses, the server
can do the same thing, we called this 'affinit
Hi,
> It's also worth noting that the old presumption that MAC-based
> interface identifiers are normal and anything else is strange is
> obsolete. See http://tools.ietf.org/html/draft-ietf-6man-ug-06
> which is approved in the RFC queue already and
> http://tools.ietf.org/html/draft-ietf-6man-def
It's also worth noting that the old presumption that MAC-based
interface identifiers are normal and anything else is strange is
obsolete. See http://tools.ietf.org/html/draft-ietf-6man-ug-06
which is approved in the RFC queue already and
http://tools.ietf.org/html/draft-ietf-6man-default-iids-00
fo
Hi,
> 1) What's the pattern with which addresses are generated/assigned? Are
> they sequential (fc00::1, fc00::2, etc.)? Random? Something else?
>
We use our dhcpy6d (http://dhcpy6d.ifw-dresden.de) which allows 4
different address categories:
- sequential range like fd00::1, fd00::2
- completely
Folks,
I'm wondering about the following two aspects of different DHCPv6
implementations out there:
1) What's the pattern with which addresses are generated/assigned? Are
they sequential (fc00::1, fc00::2, etc.)? Random? Something else?
2) What about their stability? Is there any intent/mechani
