[DHCPDISCOVER]unknown network segment.
Simon Hobson
dhcp1 at thehobsons.co.uk
Wed Oct 15 21:18:06 UTC 2014
Eugène Ngontang <sympavali at gmail.com> wrote:
> In fact I have in dhcpd conf file a block defining a subnet like this :
>
> subnet X.X.X160 netmask 255.255.255.224 {
> option routers X.X.X.161;
> option subnet-mask 255.255.255.224;
> option nis-domain "mynisdomain.com";
> option domain-name "mydomain.org";
> option domain-name-servers Y.Y.Y.3, Y.Y.Y.3;
> range X.X.X.162 X.X.X.190;
> default-lease-time 21600;
> max-lease-time 43200;
>
> }
>
> Howerver my client is not getting any ip address, and from my dhcp server I see this error in the logs :
>
> Oct 12 04:02:27 SERVERHOSTNAME dhcpd: DHCPDISCOVER from 00:aa:aa:aa:aa:aa via X.X.X.163: unknown network segment
> Oct 12 04:02:27 SERVERHOSTNAME dhcpd: DHCPDISCOVER from 00:aa:aa:aa:aa:aa via X.X.X.162: unknown network segment
Well the fact that you get packets via X.X.X.162 and X.X.X.163 suggest that there are device(s) with those addresses - the addresses should therefore **NOT** be in a dynamic pool as you have here.
But the main problem is that because you've changed things, we can't (for example) look for obvious typos. First thing to *really* check is that X.X.X is the same set of numbers in all cases - it's not hard to make a typo, and usually very hard to spot them. As an example, do you realise that you've missed a "." at the start of the subnet declaration ?
More information about the dhcp-users
mailing list