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

Groups > linux.debian.user > #264166

Re: DHCP Problem, but where

Show all headers | View raw

On 4/12/23 05:18, Geert Stappers wrote:
> That triggered me to ask "Has the DHCP server been restarted?"


The default behaviour of most dhcp clients when they can't connect to a 
dhcp server is to maintain the settings from any previous lease.

A second default behaviour is for clients to not request new dhcp until 
their existing dhcp lease has expired.

To make sure a new dhcp setting is taken by all clients you need to

-  reconfigure your dhcp server

- restart your dhcp server

- check your dhcp server logs for any problems

- restart your dhcp clients

- check your client dhcp logs to see if the new lease info has been taken.

There can be problems where a client with a specific MAC address 
requests a specific ip address based on a previous lease but the server 
is unwilling or unable to allocate that address to that MAC. This can be 
checked in the server and client logs. It may also require flushing the 
server lease tables and client configs so they can both start out 
completely fresh.

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