Re: [libvirt] [PATCH 0/2] Using client-id for DHCPv6 host identification

On 02/15/2013 02:02 PM, Gene Czarcinski wrote: > The first patch is a trivial fix to the network schema > since the name in dhcp-host is really optional. > > The second patch adds the capability to use the client id > to improve the reliability of having a system use a fixed > IPv6 address. > > Gene Czarcinski (2): > Trivial fix: in dhcp-host the name is optional > use client id for IPv6 DHCP host definition > > docs/formatnetwork.html.in | 18 ++++++- > docs/schemas/basictypes.rng | 59 > ++++++++++++++++++++++ > docs/schemas/network.rng | 7 ++- > src/conf/network_conf.c | 29 +++++++++-- > src/conf/network_conf.h | 1 + > src/network/bridge_driver.c | 3 +- > src/util/virdnsmasq.c | 20 ++++++-- > src/util/virdnsmasq.h | 1 + > tests/networkxml2confdata/dhcp6-nat-network.xml | 5 +- > tests/networkxml2confdata/dhcp6-network.xml | 5 +- > .../dhcp6host-routed-network.xml | 5 +- > 11 files changed, 138 insertions(+), 15 deletions(-) > When I originally submitted the patches for DHCPv6 I thought that using the host name for specifying hosts with fixed IPv6 addresses would work. Lots of testing proved that to be a foolish assumption. The only thing that works is to specify the ID (Client ID). This has been testing with DUID-LLT, DUID-LL, and DUID-UUID. One of the most difficult parts in this was getting the patterns in the schemas correct for the various types of DUID. I think I have tested them sufficiently but ??? One of the more difficult things was to handle bytes where the leading zero is suppressed.