Old Tired Question: 'Not configured to listen on any interfaces'

Glenn Satchell glenn.satchell at uniq.com.au
Thu Feb 24 21:24:06 UTC 2011


On 02/25/11 05:49, Simon Hobson wrote:
> Matt Causey wrote:
>
>> If it's a hard requirement for reasons that are buried in legacy
>> that's fine.
>
> It is !
> Back when the software was originally designed, non-ethernet-like
> interfaces weren't really considered. So it's fairly deeply ingrained in
> the code how it deals with interfaces - with certain assumptions.
> Similar issues affect running a relay agent where the link back to the
> server is not ethernet-like (such as a PPP link). It's to do with the
> way the server needs to be able to handle raw packets because you are
> dealing with clients that don't yet have an address.
>
> AIUI, you can compile the software to use BPF to get around the
> requirement (but then you will not be able to serve local clients), and
> you'd also have to patch the code to not complain as it is doing now.
>
 >> What I did as a workaround was created a /32 subnet declaration for
 >> the ip address on eth0 so dhcpd would run.

You should use the proper subnet for this definition. It helps dhcpd 
build an internal picture of the network structure. Something like this:

subnet a.b.c.0 netmask a.b.c.d { }

-- 
regards,
-glenn




More information about the dhcp-users mailing list