Re: [Dnsmasq-discuss] Linksys routers, bridges, network appliances: host names
Chris, Thanks. Yes, I already use the dhcp-host= option on various of these devices. I was inquiring about a more generic solution. - John -Original Message- From: Chris G c...@isbd.net Sent: Nov 19, 2010 4:35 AM To: dnsmasq-discuss@lists.thekelleys.org.uk Subject: Re: [Dnsmasq-discuss] Linksys routers, bridges, network appliances: host names On Thu, Nov 18, 2010 at 03:15:08PM -0500, John R. Graham wrote: Most of these little Linksys devices are capable of getting an IP address via DHCP from dnsmasq but none of them (that I have tried) seem capable of delivering their host name to dnsmasq as all of my Linux and Windows boxen do. Is this a known limitation of these little boxes, or do I need to do something I haven't done in the dnsmasq.conf file? I can pull a Wireshark trace of the DHCP transaction if that would be helpful. It's quite a problem with various small devices, I have a Western Digital NAS which doesn't provide itself with a name when it gets its IP from dnsmasq. I have the following at the end of my dnsmasq.conf to deal with this:- dhcp-host=00:90:a9:70:06:ff,backup -- Chris Green ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] Linksys routers, bridges, network appliances: host names
Most of these little Linksys devices are capable of getting an IP address via DHCP from dnsmasq but none of them (that I have tried) seem capable of delivering their host name to dnsmasq as all of my Linux and Windows boxen do. Is this a known limitation of these little boxes, or do I need to do something I haven't done in the dnsmasq.conf file? I can pull a Wireshark trace of the DHCP transaction if that would be helpful. Thanks in advance. - John
[Dnsmasq-discuss] What I thought was a clever idea with --dhcp-optsfile didn't work out.
Hi. I had what I thought was a clever idea to get dnsmasq to re-read it's whole dnsmasq.conf file when it received a SIGHUP signal. I invoked dnsmasq with the following command line options: -i eth0 --conf-file=/etc/dnsmasq.once.conf The dnsmasq.once.conf file was basically empty except for the single line dhcp-optsfile=/etc/dnsmasq.conf My hope was that this would cause the dnsmasq.conf file to be read at startup but this doesn't appear to be the case. Nor does it appear to be read when a SIGHUP is sent to dnsmasq. So, I tried a variation. I added conf-file=/etc/dnsmasq.conf to the dnsmasq.once.conf file. However, this created its own problems. Whenever dnsmasq was restarted, I started getting error messages of the form bad dhcp-option at line xx of /etc/dnsmasq.conf So, my question is, is what I'm trying to do a *bad* idea or am I just doing it wrong? - John
