Re: DHCP Problem, but where

2023-12-03 Thread Charles Curley
On Sun, 3 Dec 2023 22:32:59 -0500 Jeffrey Walton 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

Re: DHCP Problem, but where

2023-12-03 Thread Jeffrey Walton
On Sun, Dec 3, 2023 at 9:57 PM jeremy ardley wrote: > > > 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 prev

Re: DHCP Problem, but where

2023-12-03 Thread Charles Curley
On Sun, 3 Dec 2023 22:18:22 +0100 Geert Stappers wrote: > Has the DHCP server been restarted? Yes. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/

Re: DHCP Problem, but where

2023-12-03 Thread jeremy ardley
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

Re: DHCP Problem, but where

2023-12-03 Thread Geert Stappers
On Sun, Dec 03, 2023 at 04:03:39PM -0500, Henning Follmann wrote: > > On Dec 3, 2023, at 14:31, Charles Curley wrote: > > > > I am installing a new router which seems to work well so far. > > > > I have changed the DHCP server to use the new router's address, and shut > > the server down and rest