Remove the unspecified gateway from linux routing table

[Eugène Ngontang]

Hi,

Yes I guess there is a dhcp relay (10.10.10.18 in the below logs) :

Feb 16 12:44:45 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.21 from
00:01:80:81:39:3a via 10.10.10.18
Feb 16 12:44:45 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.21 to
00:01:80:81:39:3a via 10.10.10.18
Feb 16 13:11:23 AE-DXB-EWS2 dhcpd: DHCPREQUEST for *10.10.10.22* from
00:01:80:81:39:7b via 10.10.10.18
Feb 16 13:11:23 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 13:26:40 AE-DXB-EWS2 dhcpd: DHCPDISCOVER from 00:01:80:81:39:3a via
10.10.10.18
Feb 16 13:26:40 AE-DXB-EWS2 dhcpd: DHCPOFFER on 10.10.10.21 to
00:01:80:81:39:3a via 10.10.10.18
Feb 16 13:26:40 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.21
(11.12.254.100) from 00:01:80:81:39:3a via 10.10.10.18
Feb 16 13:26:40 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.21 to
00:01:80:81:39:3a via 10.10.10.18
Feb 16 13:39:19 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.22 from
00:01:80:81:39:7b via 10.10.10.18
Feb 16 13:39:19 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 15:20:48 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.22 from
00:01:80:81:39:7b via 10.10.10.18
Feb 16 15:20:48 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 15:31:31 AE-DXB-EWS2 dhcpd: DHCPDISCOVER from 00:01:80:81:39:7b via
10.10.10.18
Feb 16 15:31:31 AE-DXB-EWS2 dhcpd: DHCPOFFER on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 15:31:31 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.22
(11.12.254.100) from 00:01:80:81:39:7b via 10.10.10.18
Feb 16 15:31:31 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 15:35:57 AE-DXB-EWS2 dhcpd: DHCPDISCOVER from 00:01:80:81:39:86 via
10.10.10.18
Feb 16 15:35:57 AE-DXB-EWS2 dhcpd: DHCPOFFER on 10.10.10.23 to
00:01:80:81:39:86 via 10.10.10.18
Feb 16 15:35:57 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.23
(11.12.254.100) from 00:01:80:81:39:86 via 10.10.10.18
Feb 16 15:35:57 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.23 to
00:01:80:81:39:86 via 10.10.10.18
Feb 16 15:38:01 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.21 from
00:01:80:81:39:3a via 10.10.10.18
Feb 16 15:38:01 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.21 to
00:01:80:81:39:3a via 10.10.10.18
Feb 16 15:44:18 AE-DXB-EWS2 dhcpd: DHCPDISCOVER from 00:01:80:81:39:7b via
10.10.10.18
Feb 16 15:44:18 AE-DXB-EWS2 dhcpd: DHCPOFFER on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 15:44:18 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.22
(11.12.254.100) from 00:01:80:81:39:7b via 10.10.10.18
Feb 16 15:44:18 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 16:00:34 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.22 from
00:01:80:81:39:7b via 10.10.10.18
Feb 16 16:00:34 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 17:20:59 AE-DXB-EWS2 dhcpd: DHCPDISCOVER from 00:01:80:81:39:7b via
10.10.10.18
Feb 16 17:20:59 AE-DXB-EWS2 dhcpd: DHCPOFFER on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 17:20:59 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.22
(11.12.254.100) from 00:01:80:81:39:7b via 10.10.10.18
Feb 16 17:20:59 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 16 17:34:52 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.21 from
00:01:80:81:39:3a via 10.10.10.18
Feb 16 17:34:52 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.21 to
00:01:80:81:39:3a via 10.10.10.18
Feb 17 15:21:26 AE-DXB-EWS2 dhcpd: DHCPDISCOVER from 00:01:80:81:39:7b via
10.10.10.18
Feb 17 15:21:26 AE-DXB-EWS2 dhcpd: DHCPOFFER on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18
Feb 17 15:21:26 AE-DXB-EWS2 dhcpd: DHCPREQUEST for 10.10.10.22
(11.12.254.100) from 00:01:80:81:39:7b via 10.10.10.18
Feb 17 15:21:26 AE-DXB-EWS2 dhcpd: DHCPACK on 10.10.10.22 to
00:01:80:81:39:7b via 10.10.10.18

You can see the system I dealing with (10.10.10.22) is not the only one.

Regards,
Eugène NG

2015-02-17 13:24 GMT+01:00 Niall O'Reilly <niall.oreilly at ucd.ie>:

> At Tue, 17 Feb 2015 12:16:07 +0100,
> Rudy Zijlstra wrote:
> >
> > The correct question is indeed posed by the OP, which is why the
> > gateway is not applied from the DHCP response.
>
>   +1
>
> > Some questions:
> > - which distribution is this?
> > - is dhcp provided by the a package from the distribution, or is it
> > hand compiled?
> > - which release of dhclient/dhcp is in use?
> > - dhclient typically calls a script to set the values. Is this script
> > correct and in place?
>
>   I would add:
>
>   - Are the client ("remote linux machine") and DHCP server connected
>     to the same network?
>   - If not, is a DHCP relay in use?
>   - What is shown in the DHCP server logs?
>   - What is shown in the *client* leases file?
>   - Is the DHCP response actually reaching the client, and in good time?
>     [The presence of a route for 169.254.0.0/16 suggests to me not.]
>
>   Niall O'Reilly
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>



-- 
ngonta_e at epitech.net
sympavali at gmail.com
------------------------------------------------------------
*Aux hommes il faut un chef, et au*

* chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te
voit on te juge!*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150217/ccf3d72e/attachment.html>