Re: DHCP Problem, but where

From	Charles Curley <charlescurley@charlescurley.com>
Newsgroups	linux.debian.user
Subject	Re: DHCP Problem, but where
Date	2023-12-04 04:50 +0100
Message-ID	<HH881-aVBV-1@gated-at.bofh.it> (permalink)
References	<HH0tP-aQOx-5@gated-at.bofh.it> <HH1SY-aRP3-23@gated-at.bofh.it> <HH22B-aRSU-1@gated-at.bofh.it> <HH2lX-aS07-1@gated-at.bofh.it> <HH7Yl-aVyE-1@gated-at.bofh.it>
Organization	occasionally

Show all headers | View raw

On Sun, 3 Dec 2023 22:32:59 -0500
Jeffrey Walton <noloader@gmail.com> wrote:

> The "restart your dhcp clients" may have a sharp edge. Sometimes the
> clients have a touch of resiliency or hardening added so they contact
> their original dhcp server, and not a [possibly] rogue server setup by
> an unknowing developer or attacker. In the past, you used to have to
> reboot Microsoft clients to get them to use the new dhcp server. I
> don't know Linux behavior.
> 
> But if the problem is, dhcp clients are using the old dhcp server or
> old dhcp lease info, then I would try to reboot a client if the
> service restart did not help.

I think the ISC dhclient (which is what I use here) does try to return
to its original server. Rather than reboot anything, I simply stopped
the DHCP server on that machine. Apparently clients then started back at
the beginning. Shortening the lease time accelerates that process.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Thread

DHCP Problem Charles Curley <charlescurley@charlescurley.com> - 2023-12-03 20:40 +0100
  Re: DHCP Problem Marco Moock <mm@dorfdsl.de> - 2023-12-03 21:00 +0100
    Re: DHCP Problem Charles Curley <charlescurley@charlescurley.com> - 2023-12-03 22:30 +0100
  Re: DHCP Problem Henning Follmann <hfollmann@itcfollmann.com> - 2023-12-03 22:10 +0100
    Re: DHCP Problem, but where Geert Stappers <stappers@stappers.nl> - 2023-12-03 22:20 +0100
      Re: DHCP Problem, but where jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-03 22:40 +0100
        Re: DHCP Problem, but where Jeffrey Walton <noloader@gmail.com> - 2023-12-04 04:40 +0100
          Re: DHCP Problem, but where Charles Curley <charlescurley@charlescurley.com> - 2023-12-04 04:50 +0100
      Re: DHCP Problem, but where Charles Curley <charlescurley@charlescurley.com> - 2023-12-03 22:40 +0100
  goose DHCP clients to new address   Was: DHCP Problem Geert Stappers <stappers@stappers.nl> - 2023-12-03 22:20 +0100
    Re: goose DHCP clients to new address   Was: DHCP Problem Charles Curley <charlescurley@charlescurley.com> - 2023-12-03 23:00 +0100
      Re: goose DHCP clients to new address Was: DHCP Problem Jeffrey Walton <noloader@gmail.com> - 2023-12-03 23:20 +0100
        Re: goose DHCP clients to new address Was: DHCP Problem Charles Curley <charlescurley@charlescurley.com> - 2023-12-04 00:00 +0100
  Re: DHCP Problem Charles Curley <charlescurley@charlescurley.com> - 2023-12-04 04:50 +0100
  Re: DHCP Problem <tomas@tuxteam.de> - 2023-12-04 06:00 +0100
    Re: DHCP Problem Charles Curley <charlescurley@charlescurley.com> - 2023-12-04 07:10 +0100

csiph-web