[Bug 991360] Re: isc-dhcp-client does not send hostnames in DHCPv6 by default

Martin Jackson martin.h.jackson at gmail.com
Tue Jun 26 22:32:16 UTC 2012


Hi Stephane,

Sorry, I should have been clearer about that.  I believe that I observed
that the "<hostname>" magic only works with "option host-name" in the
dhclient.conf file.  4.2 helps with this because it has the more
generalized hostname() function which should be accepted in more places
in the dhclient.conf file, such as after fqdn.fqdn.  Sending a string
hostname is nice, but that would require some way to populate fqdn.fqdn
with the desired hostname - and that's something that even upstream
(finally) agrees is something dhclient itself should know how to do.

The big question, I think, is whether there should be a separate
dhclient6.conf file or not.  I'm inclined to think there should be
separate files; but that's just my opinion.  I don't think it would be
harmful to send fqdn.fqdn to a DHCPv4 server, but I don't know if people
would expect that behavior from stock dhclient.  Windows XP+ send both
Option 12 (host-name) and Option 81 (fqdn.fqdn), and most of the DHCP
servers I've run handle that just fine.  But still, since options have
different numbers and the wire protocol is so different, that means that
DHCPv4 and DHCPv6 are effectively different services and should be
orthogonal to each other.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/991360

Title:
  isc-dhcp-client does not send hostnames in DHCPv6 by default

Status in “isc-dhcp” package in Ubuntu:
  In Progress

Bug description:
  DHCPv6 does not have a host-name option to send the client hostname to
  register with the DHCP server.  There are several potential options
  here:

  1)  Use the same "magic" to insert the hostname via fqdn.fqdn (i.e. "send fqdn.fqdn "<hostname>";"  This should work with DHCPv4 as well.
  2)  Backport the gethostname() functionality from DHCP 4.2.
  3)  Upgrade to isc-dhcp-client 4.2.

  Perhaps some of these are more appropriate to consider for the Q
  cycle.  Personally, I think option 1 (implementing "<hostname>" magic)
  for fqdn.fqdn would be the least intrusive.

  As issues go, this is admittedly minor.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: isc-dhcp-client 4.1.ESV-R4-0ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CheckboxSubmission: 014d169fc2d78562c156088c6ab6adc0
  CheckboxSystem: c69722ecac764861be52925fa50b4dcc
  Date: Sun Apr 29 13:19:49 2012
  DhclientLeases:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to precise on 2012-04-15 (14 days ago)
  mtime.conffile..etc.dhcp.dhclient.conf: 2011-09-26T21:03:34.986111

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/991360/+subscriptions




More information about the foundations-bugs mailing list