Bugzilla – Bug 1264
send some default client host name to DHCP servers when requesting an ip
Last modified: 2009-09-08 09:15:35 UTC
not sure how this would work though, can't really find it in the rfc for dhcp, maybe it's in some of the extensions rfc's?
Could we possibly update the flash on the device so that a default string gets overwritten with the Player Name as specified in the web interface? Customer request about this issue: Why does my Netgear FWG114P list my Squeezeboxes as UNKNOWN NAME but my computers by their hostname_ Can you or I fix it please? I have three of the stupidly-named things and have to rely on the IP address to tell one from tother. Attached Devices ---------------------------------------------------------------------------------------- PCs and Devices currently on the Network ------------------------------------------------------------- # Device Name IP Address MAC Address 1 10.10.19.1 UNKNOWN NAME 00:04:20:05:06:d3 2 10.10.19.2 UNKNOWN NAME 00:04:20:05:55:5b 3 10.10.19.3 UNKNOWN NAME 00:04:20:05:3b:bf 4 10.10.19.5 GERMAN 00:09:5b:94:71:b7 5 10.10.19.8 SPIDER 00:03:ba:08:5c:82 6 10.10.19.90 SPARKY 08:00:20:b9:71:3f ---------------------------------------------------------------------------------------- I have given them names in the Player Settings inthe web interface of SlimServer: ================================================================ Player Name ------------------- You can give this player a name that will be used to identify the player on these web pages. Player name: Bedroom Player [Change] ================================================================
Looks like this is the right bug for DHCP Client ID. Please assign a default DHCP Client ID value; if the user assigns a name to the client unit, use the assigned name.
To use the player name as a DHCP hostname it would have to conform to the formatting rules for hosts and be saved in the player firmware, which could open a whole new can of worms. I don't think it's worth it since you can always let the DHCP server assign a host name to the squeezebox via its MAC address.
I begin to wonder if the reassignment of my SqueezeBox's IP has to do with the fact that it's the only device in my network that doesn't send a DHCP name to the server. Indeed I observe that it constantly gets new IP addresses, sometimes even in/after periods of standby. I tend to think that sending no name to the server is more than a cosmetic bug. Maybe for a first step it would be enough to derive a unique name from the MAC (Like "queezebox-MAC"). This should be pretty easy to implement.
Definition of Client ID, per RFC 2131 http://www.faqs.org/rfcs/rfc2131.html "DHCP defines a new 'client identifier' option that is used to pass an explicit client identifier to a DHCP server. This change eliminates the overloading of the 'chaddr' field in BOOTP messages, where 'chaddr' is used both as a hardware address for transmission of BOOTP reply messages and as a client identifier. The 'client identifier' is an opaque key, not to be interpreted by the server; for example, the 'client identifier' may contain a hardware address, identical to the contents of the 'chaddr' field, or it may contain another type of identifier, such as a DNS name. The 'client identifier' chosen by a DHCP client MUST be unique to that client within the subnet to which the client is attached. If the client uses a 'client identifier' in one message, it MUST use that same identifier in all subsequent messages, to ensure that all servers correctly identify the client." The DHCP Client ID is not a hosname (although it can be if desired), nor is it a MAC address (although it can be if desired). If DHCP Client ID is supported, we simplly have an *option* for the Squeezebox to label itself in the DHCP client lists in a human-friendly manner.
Subject: Out of Office AutoReply: send some default client host name to DHCP servers when requesting an ip I'm currently out of the office until Monday, 3rd July, and will have no access to e-mail during this time. Please contact Justin Kidder with any urgent items. Best regards, Chris <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0"> <TITLE>Out of Office AutoReply: [Bug 1264] send some default client host name to DHCP servers when requesting an ip</TITLE> </HEAD> <BODY> <!-- Converted from text/plain format --> <P><FONT SIZE=2>I'm currently out of the office until Monday, 3rd July, and will have no access to e-mail during this time. Please contact Justin Kidder with any urgent items.<BR> <BR> Best regards,<BR> <BR> Chris</FONT> </P> </BODY> </HTML>
This bug is fixed in firmware 56. It is currently undergoing internal testing. You will be notified again when it is made part of a nightly release.
I apologize; I've been slow in adding this notification to some of the bugs. Please ignore it if you've already tried the new firmware. This bug fix is now available in the nightly Slimserver release. The release is available from: http://www.slimdevices.com/dev_nightly.html If you prefer to wait for the next official release, you will be notified when it occurs. You'll need to install the new version of Slimserver, and then force your Squeezebox to upgrade its firmware by holding down the 'Brightness' button on the remote control until the firmware upgrade process begins. If you are still experiencing this problem after upgrading your affected players to the new firmware, please reopen the bug.