Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264184
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: DHCP Problem |
| Date | 2023-12-04 04:50 +0100 |
| Message-ID | <HH881-aVBV-3@gated-at.bofh.it> (permalink) |
| References | <HH0tP-aQOx-5@gated-at.bofh.it> |
| Organization | occasionally |
On Sun, 3 Dec 2023 12:30:53 -0700 Charles Curley <charlescurley@charlescurley.com> 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 restarted it. Existing clients insist on > using the old router anyway. Is there any way to goose clients into > using the new one short of manually using the ip route command? > > OK, stupid mistake of the week. The frustrating problem was that the clients kept getting the old router's IP address. This was for the simple reason that I had managed to not change the value of the "option routers" entry for the subnet. Doh! I have fixed that. Never be afraid to recheck your own work. I did shorten the lease times and that has accelerated the changeover. I didn't need to restart all the client's leases. Two days hence I'll change them back. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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