On Fri, Dec 26, 2008 at 18:18, Geoffrey Leach <[email protected]> wrote: > On 12/25/2008 05:39:01 PM, Rune Kock wrote: >> Hi Geoffrey >> >> On Fri, Dec 26, 2008 at 01:13, Geoffrey Leach <[email protected]> >> wrote: >> > I'm attempting to connect an HDHR (see thread elsewhere). Every >> time >> > the HDHR sends out a DHCP Discover packet, dnsmasq says: >> > >> > dnsmasq: no address range available for DHCP request via eth0 >> > >> > Config is attached, but the relevant option would seem to be >> > >> > dhcp-range=192.168.10.5,192.168.10.10 >> > >> > Can someone interpret or, better yet, point me to a list of such >> > messages? >> >> If your eth0 still doesn't have an IP-address, then that is probably >> the problem. >> >> Dnsmasq checks that the dhcp-range matches the subnet that the >> interface uses. It likely discards your dhcp-range setting, if eth0 >> doesn't have an 192.168.10.xxx address. > > Hmmmm .... clearly I need training! I was under the impression that a > DHCP Discover packet is sent for the purpose of being assigned an IP > address. What am I missing?
You're right that the client (HDHR) sends a discover packet as part of the process of getting an address. But on the server (PVR - the machine running dnsmasq), the interface used (eth0) must have an address already. Typically, that interface is configured manually with a static address.
