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


Groups > linux.debian.user > #264186

Re: DHCP Problem

From <tomas@tuxteam.de>
Newsgroups linux.debian.user
Subject Re: DHCP Problem
Date 2023-12-04 06:00 +0100
Message-ID <HH9dL-aWPu-1@gated-at.bofh.it> (permalink)
References <HH0tP-aQOx-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Sun, Dec 03, 2023 at 12:30:53PM -0700, 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 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?

Wait a sec: before the clients get an answer from the DHCP server, they
don't have any route (at least not for the network in question), so it
doesn't make sense poking at them with ip route and things. They send their
request to the local network's segment broadcast address.

What's possibly happening is that your old DCHP server is still up and
running and faster than your new one, so its answers come in first.

Cheers
-- 
t

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