Re: goose DHCP clients to new address Was: DHCP Problem
On Sun, 3 Dec 2023 17:18:23 -0500
Jeffrey Walton <noloader@gmail.com> wrote:
> I don't know about Linux clients, but in the past, Windows clients
> used to try to connect to the previous DHCP server for its lease info.
> If the old DHCP server is still available (on the old router?), then
> the client may be getting the lease info from the old server. To avoid
> the problem, we disconnected the old server from the network.
I did shut down both the old server and its failover peer. Clients I
haven't mucked with are now asking for leases from the new server.
Dec 03 14:55:48 issola dhcpd[24072]: failover peer failover-partner: I move from startup to communications-interrupted
Dec 03 15:09:46 issola dhcpd[24072]: DHCPREQUEST for 192.168.100.45 from ec:28:d3:7a:6a:76 via enp1s0
Dec 03 15:09:46 issola dhcpd[24072]: DHCPACK on 192.168.100.45 to ec:28:d3:7a:6a:76 via enp1s0
Dec 03 15:40:50 issola dhcpd[24072]: DHCPREQUEST for 192.168.100.45 from ec:28:d3:7a:6a:76 via enp1s0
Dec 03 15:40:50 issola dhcpd[24072]: DHCPACK on 192.168.100.45 to ec:28:d3:7a:6a:76 via enp1s0
But that guy is still pointing toward the old router.
>
> You should probably just perform a hard cut-over. Shutdown the old
> router, stand up the new router. After the hard cutover, force clients
> to renew their leases (or wait until they do it on their own). And if
> things go sideways, undo the change.
I may yet do that. The change will consist of pulling the Ethernet cable
between the old router and its upstream connection.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: