Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. isc dhcp server and client query (Asma Kouser)
2. Re: Question (Leslie Rhorer)
----------------------------------------------------------------------
Message: 1
Date: Fri, 3 Jun 2022 10:53:55 +0530 (IST)
From: Asma Kouser <kous...@medha.com>
To: dhcp-users <dhcp-users@lists.isc.org>
Subject: isc dhcp server and client query
Message-ID:
<1276833269.3187553.1654233835687.javamail.zim...@medha.com>
Content-Type: text/plain; charset="utf-8"
Hi there,
I am using ISC DHCP-4.3.6, and have a scenario in which the server is not
allocating the IP address. I have updated the dhcpd.conf to give an IP address
based on 'agent.circuit-id' and 'agent.remote-id' and there is only one IP in
the pool to assign. When I connect a laptop the switch will add the agent info
and forward it to the DHCP server and the DHCP server assigned the address
which is defined in the Pool. now I have removed this laptop and connected
another laptop on the same port, now the hardware address and the hostname will
change but the agent information remains the same, in this case, the server is
not allocating the IP address and says no free lease. Please let me know what
modifications should i made to get the IP address for the second laptop.
Also, the ISC DHCP client does not send a DHCP Discovery or a request when the
ethernet link is down and up again. Please let me know what modifications
should I do to achieve this as well.
Regards,
Asma Kouser
Manager R&D
Emp Code: 901567
Ext Num: 7295
Contact Num: 9177359511
*******************************************************************************************
Disclaimer:The information contained in this e-mail and/or attachments to it
may contain confidential data (or) privileged information of Medha. If you are
not the intended recipient, any dissemination, use in any manner, review,
distribution, printing, copying of the information contained in this e-mail
and/or attachments to it are strictly prohibited. If you have received this
communication in error, please notify the sender and immediately delete the
message and attachments (if any) permanently.
"Please consider the environment before printing this message."
*******************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20220603/64dc7fd3/attachment-0001.htm>
------------------------------
Message: 2
Date: Fri, 3 Jun 2022 00:26:35 -0500
From: Leslie Rhorer <lesrho...@siliconventures.net>
To: dhcp-users@lists.isc.org
Subject: Re: Question
Message-ID: <16b1f80f-19db-acc3-1eb4-e76db6e4a...@siliconventures.net>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 6/2/2022 11:30 PM, Gregory Sloop wrote:
>
> I'm not at all sure your servers are running well, or that they're
> handling leases the way you think.
>
??? That may well be true.? Certainly I was unaware of the split directive
>
> One probably trivial thing.
>
> In the config you sent, you have a very odd split, of zero.
>
> That forces all the balance to one side. Toward the secondary, IIRC.
> Perhaps you're only testing something I don't know. I think 128 is a
> "normal" split. (I don't think there's any good reason not to balance
> them evenly - at least I've never heard a use case that made sense.)
>
??? Fixed (or at least set to 128).
>
> More toward things that sure seem like symptoms of your peers not
> communicating properly.
>
> In the logs;
>
> Do you see the two peers go to "normal" when you start them both up.
> And interrupted when one is down?
>
> something like:
>
> failover peer dhcp-failover: peer moves from normal to
> communications-interrupted
>
> failover peer dhcp-failover: I move from startup to normal
>
> failover peer dhcp-failover: peer moves from
> communications-interrupted to normal
>
> failover peer dhcp-failover: Both servers normal
>
??? No, at this point, neither one is reporting a normal status, either
to or from.? In the log file, the secondary shows
Jun? 2 23:50:16 Backup dhcpd[70691]: Server starting service.
Jun? 2 23:50:16 Backup dhcpd[70691]: Failover CONNECTACK from
dhcp-failover: already connected
Jun? 2 23:50:16 Backup dhcpd[70691]: failover peer dhcp-failover: I move
from startup to recover
Jun? 2 23:50:16 Backup dhcpd[70691]: dhcp_failover_put_message:
something went wrong.
Jun? 2 23:50:16 Backup dhcpd[70691]: peer dhcp-failover: disconnected
Jun? 2 23:50:21 Backup dhcpd[70691]: Failover CONNECTACK from
dhcp-failover: already connected
Jun? 2 23:50:21 Backup dhcpd[70691]: failover peer dhcp-failover: peer
moves from recover to recover
Jun? 2 23:50:21 Backup dhcpd[70691]: failover peer dhcp-failover:
requesting full update from peer
Jun? 2 23:50:21 Backup dhcpd[70691]: dhcp_failover_put_message:
something went wrong.
Jun? 2 23:50:21 Backup dhcpd[70691]: peer dhcp-failover: disconnected
Jun? 2 23:50:21 Backup dhcpd[70691]: Failed to send update request all
message to dhcp-failover: socket is not connected
Jun? 2 23:50:26 Backup dhcpd[70691]: Failover CONNECTACK from
dhcp-failover: already connected
Jun? 2 23:50:26 Backup dhcpd[70691]: failover peer dhcp-failover: peer
moves from recover to recover
Jun? 2 23:50:26 Backup dhcpd[70691]: failover peer dhcp-failover:
requesting full update from peer
Jun? 2 23:50:26 Backup dhcpd[70691]: dhcp_failover_put_message:
something went wrong.
Jun? 2 23:50:26 Backup dhcpd[70691]: peer dhcp-failover: disconnected
Jun? 2 23:50:26 Backup dhcpd[70691]: Failed to send update request all
message to dhcp-failover: socket is not connected
??? In the leases file, the secondary shows
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.4.1
# authoring-byte-order entry is generated, DO NOT DELETE
authoring-byte-order little-endian;
failover peer "dhcp-failover" state {
? my state recover at 1 2022/05/30 09:56:55;
? partner state recover at 5 2022/06/03 04:42:48;
}
failover peer "dhcp-failover" state {
? my state recover at 1 2022/05/30 09:56:55;
? partner state recover at 5 2022/06/03 04:42:48;
}
server-duid "\000\001\000\001*'QgPF]e\025\234";
failover peer "dhcp-failover" state {
? my state recover at 1 2022/05/30 09:56:55;
? partner state recover at 5 2022/06/03 04:42:48;
}
failover peer "dhcp-failover" state {
? my state recover at 1 2022/05/30 09:56:55;
? partner state recover at 5 2022/06/03 04:50:21;
}
failover peer "dhcp-failover" state {
? my state recover at 1 2022/05/30 09:56:55;
? partner state recover at 5 2022/06/03 04:50:26;
}
??? In the log file, the primary shows
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: Internet Systems Consortium
DHCP Server 4.4.1
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: Copyright 2004-2018 Internet
Systems Consortium.
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: All rights reserved.
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: For info, please visit
https://www.isc.org/software/dhcp/
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: Wrote 0 deleted host decls to
leases file.
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: Wrote 0 new dynamic host decls
to leases file.
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: Wrote 0 leases to leases file.
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: failover peer dhcp-failover: I
move from recover to startup
Jun? 2 23:40:57 RAID-Server dhcpd[5057]: Server starting service.
Jun? 2 23:41:12 RAID-Server dhcpd[5057]: failover peer dhcp-failover: I
move from startup to recover
Jun? 2 23:41:12 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 2 23:41:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)
Jun? 2 23:41:25 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 2 23:41:25 RAID-Server dhcpd[5057]: DHCPREQUEST for 0.0.0.0 from
20:17:42:1e:51:d5 via enp6s0: unknown lease 0.0.0.0.
Jun? 2 23:41:33 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 2 23:41:41 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 2 23:41:54 RAID-Server dhcpd[5057]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp6s0: not responding (recovering)
Jun? 2 23:42:00 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 2 23:42:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)
Jun? 2 23:42:28 RAID-Server dhcpd[5057]: Failover CONNECTACK from
dhcp-failover: already connected
Jun? 2 23:42:28 RAID-Server dhcpd[5057]: failover peer dhcp-failover:
peer moves from recover to recover
Jun? 2 23:42:28 RAID-Server dhcpd[5057]: failover peer dhcp-failover:
requesting full update from peer
Jun? 2 23:42:28 RAID-Server dhcpd[5057]: dhcp_failover_put_message:
something went wrong.
Jun? 2 23:42:28 RAID-Server dhcpd[5057]: peer dhcp-failover: disconnected
Jun? 2 23:42:28 RAID-Server dhcpd[5057]: Failed to send update request
all message to dhcp-failover: socket is not connected
Jun? 2 23:42:33 RAID-Server dhcpd[5057]: peer dhcp-failover: disconnected
Jun? 2 23:42:38 RAID-Server dhcpd[5057]: peer dhcp-failover: disconnected
Jun? 2 23:42:38 RAID-Server dhcpd[5057]: Failover CONNECTACK from
dhcp-failover: already connected
Jun? 2 23:42:38 RAID-Server dhcpd[5057]: failover peer dhcp-failover:
peer moves from recover to recover
Jun? 2 23:42:38 RAID-Server dhcpd[5057]: failover peer dhcp-failover:
requesting full update from peer
Jun? 2 23:42:38 RAID-Server dhcpd[5057]: dhcp_failover_put_message:
something went wrong.
Jun? 2 23:42:38 RAID-Server dhcpd[5057]: peer dhcp-failover: disconnected
...
Jun? 3 00:17:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)
Jun? 3 00:17:44 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 3 00:17:55 RAID-Server dhcpd[5057]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp6s0: not responding (recovering)
Jun? 3 00:17:56 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 3 00:18:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)
Jun? 3 00:18:16 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 3 00:18:23 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 3 00:18:55 RAID-Server dhcpd[5057]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp6s0: not responding (recovering)
Jun? 3 00:18:55 RAID-Server dhcpd[5057]: DHCPREQUEST for 192.168.1.66
from 20:17:42:1e:51:d5 via enp6s0
Jun? 3 00:18:55 RAID-Server dhcpd[5057]: DHCPACK on 192.168.1.66 to
20:17:42:1e:51:d5 via enp6s0
Jun? 3 00:19:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)
Jun? 3 00:19:36 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 3 00:19:51 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 3 00:19:55 RAID-Server dhcpd[5057]: DHCPDISCOVER from
60:01:94:f0:41:48 via enp6s0: not responding (recovering)
Jun? 3 00:20:12 RAID-Server dhcpd[5057]: DHCPDISCOVER from
64:db:a0:15:55:e0 via enp6s0: not responding (recovering)
Jun? 3 00:20:14 RAID-Server dhcpd[5057]: DHCPDISCOVER from
d8:1f:12:6a:8e:9b via enp6s0: not responding (recovering)
Jun? 3 00:20:22 RAID-Server dhcpd[5057]: DHCPREQUEST for 192.168.0.18
from 68:57:2d:a9:b0:f8 via enp6s0
Jun? 3 00:20:22 RAID-Server dhcpd[5057]: DHCPACK on 192.168.0.18 to
68:57:2d:a9:b0:f8 via enp6s0
Jun? 3 00:20:45 RAID-Server dhcpd[5057]: DHCPREQUEST for 192.168.0.23
from 68:57:2d:a9:b3:38 via enp6s0
Jun? 3 00:20:45 RAID-Server dhcpd[5057]: DHCPACK on 192.168.0.23 to
68:57:2d:a9:b3:38 via enp6s0
??? And in the leases file
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.4.1
# authoring-byte-order entry is generated, DO NOT DELETE
authoring-byte-order little-endian;
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 1 2022/05/30 09:57:06;
}
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 1 2022/05/30 09:57:06;
}
server-duid "\000\001\000\001%\325\"\211\010bf\241@\223";
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 1 2022/05/30 09:57:06;
}
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 5 2022/06/03 04:42:28;
}
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 5 2022/06/03 04:42:38;
}
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 5 2022/06/03 04:42:43;
}
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 5 2022/06/03 04:42:48;
}
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 5 2022/06/03 04:42:53;
}
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 5 2022/06/03 04:50:16;
}
failover peer "dhcp-failover" state {
? my state recover at 2 2020/02/11 08:30:01;
? partner state recover at 5 2022/06/03 04:50:26;
}
(Continued)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20220603/82a58352/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 164, Issue 6
******************************************
