Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #264171

Re: goose DHCP clients to new address Was: DHCP Problem

Show all headers | View raw

On Sun, Dec 3, 2023 at 4:51 PM Charles Curley
<charlescurley@charlescurley.com> wrote:
>
> On Sun, 3 Dec 2023 22:14:51 +0100
> Geert Stappers <stappers@stappers.nl> wrote:
>
> > I assume that the previous router is disconnected from the LAN.
>
> No. Until I solve this problem (and a few others), I will have clients
> using the old router.
>
> > The DHCProtocol has "release" for such goosing.
> > At DHCPclient do "stop DHCP", over the wire goes DHCPRELEASE [0]
> > The DHCPclient should forget ( "release" ) previous settings.
> > At DHCPclient do "start DHCP", client should get fresh config,
> > including the setting for the fresh router.
>
> I'm not sure how to do this. I did run on a client
>
> dhclient -r
> dhclient
>
> I observed no changes.
>
> The -r causes dhclient to release its lease. Invoking dhclient again
> should then obtain a new lease.

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.

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.

> > If that is already done, provide information to enable further help.
> > Such as name of the DHCP client program  and DHCP lease time.
>
> I am using whatever is standard on Debian Bullseye and Bookworm.
>
> root@hawk:/etc# pre dhc
> isc-dhcp-client 4.4.1-2.3+deb11u2               amd64
> isc-dhcp-common 4.4.1-2.3+deb11u2               amd64
> root@hawk:/etc#
>
> root@tiassa:~# pre dhc
> isc-dhcp-client 4.4.3-P1-2              amd64
> isc-dhcp-common 4.4.3-P1-2              amd64
> root@tiassa:~#
>
> The client's name is dhclient.
>
> default-lease-time 86400; # 24 hours
> max-lease-time 172800;    # 48 hours
>
> I think for the purposes of experimentation I will shorten those to
> half an hour and one hours respectively.

Jeff

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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