Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: The Natural Philosopher Newsgroups: comp.os.linux.misc Subject: I never thought of this scenario Date: Sun, 7 Apr 2024 10:45:39 +0100 Organization: A little, after lunch Lines: 26 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sun, 07 Apr 2024 09:45:40 +0200 (CEST) Injection-Info: dont-email.me; posting-host="8bdaa0523840cb4dfb7b11fcc8d732c2"; logging-data="2860861"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18YkGOmv7grZXuYuXnpCRFI+zy5BU+CRKc=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:SK/0oeRMA2RvcKaSfhLwwJoPopc= Content-Language: en-GB Bytes: 1760 I decided on a quiet breezy Sunday morning, to upgrade my routers firmware. Which required a router reboot. So it lost all its DHCP tables. However apart from 10 seconds of internet outage, the rest of the network carried on nicely (nothing uses the router's wifi, as it's in a remote space). I then restarted a piece of kit I am working on, and it popped up in the first available DHCP slot. My question is, if that had already been occupied by another piece of kit, would I have ended up with an IP address clash? It seems to me that checking for conflicts only happens at lease start or lease renewal times? Or does that imply that the router did check the ip address first before allocating the IP? -- Canada is all right really, though not for the whole weekend. "Saki"