[DHCPDISCOVER]unknown network segment.

Eugène Ngontang sympavali at gmail.com
Thu Oct 16 09:20:37 UTC 2014


Yes Simon exactly. But as you the subnet is declared. That's why I'm then
confused, and want to know what other reason can cause this. I have not
seen any real document about this issue.
Thanks.
Le 16 oct. 2014 11:10, "Simon Hobson" <dhcp1 at thehobsons.co.uk> a écrit :

> Eugène Ngontang <sympavali at gmail.com> wrote:
>
> > range      X.X.X.162 X.X.X.190;
>
> No.
> You have devices at .162 and .163, see the "via ..." bit here :
>
> > > 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
>
> These addresses are also in the range you have specified so the server can
> attempt to give them to other clients. This is "a bad thing". So as a
> minimum you need to change your range statement to "X.X.X.164 X.X.X.190" -
> and if you have any other devices with addresses in that range then they
> need excluding too.
>
> However, that still doesn't address your main problem. "unknown network
> segment" normally means that there is no subnet declaration which includes
> the IP address of the relay agent.
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20141016/e62be7ec/attachment.html>


More information about the dhcp-users mailing list