On Sun 15 Nov 2026 at 17:23:28 (+0000), Joe wrote: > On Sun, 15 Nov 2026 17:07:45 -0000 (UTC) CGS wrote: > > On 2024-10-13, <[email protected]> <[email protected]> wrote: > > > > > > > > > You /can/ tell the DHCP server (possibly running on "the router") > > > to always assign the same IP to a given client (whatever a "gien > > > client" is in this context -- identified by the MAC or other > > > means). > > > > Static IP. > > No, it's a DHCP reservation. It behaves like a static IP, but allows > the DHCP server to provide other information, such as the domain name, > extra routes and other stuff. It also allows the workstation to be a > standard DHCP client, so if it is a laptop it can be connected to some > other network and pick up information automatically from there, with no > manual intervention. More versatile, but more things to fail. > > > > > But the OP wants, as far as I understand, a *static* IP. Then, no > > > DHCP is involved at all (and no router or any other external > > > piece). > > > > I'm not following. > > > An actual static IP is handcoded into the client machine, and does not > accept any information from a DHCP server. Less to fail, less versatile. > If the network router has to change its IP address, all the client > machines with static addressing have to be reconfigured, that would > happen automatically with DHCP. > > Which is easier or more convenient depends on the number of computers > in the network and how they are used.
It might be interesting to know why the OP wanted static addresses. I want /stable/ and memorable hostnames and addresses on my home network for communicating with them by name, considering that I have no DNS service on the network. My method is to set up my "edge" router (next to the modem) as the DHCP server, assigning names and addresses for all the devices on my network, PCs, TV boxes, mobiles, printers, and the other two routers.¹ The latter are dumb bridges for ethernet and wifi (all with the same SSID). Using DHCP-assigned names and addresses is easier than finding out how to set them on every non-computer device, and prevents the risk of two devices having the same address. From the edge router's list of IP assignments, I generate a master list of all our devices in /etc/hosts format, distributed to the PCs. I run a simple script to alter the appropriate line in the master list and send/install the resulting file onto each PC's /etc/hosts; eg it changes: 192.168.1.17 argo.corp argo to: 127.0.1.1 argo.corp argo # 192.168.1.17 for argo. With no argument, the script installs /etc/hosts locally; with a hostname argument, it sends it over to that host. When I travel, there's no conflict between my home configuration files and whatever network configuration is negotiated between the laptop and the wifi service provided. ¹ all assigned by MAC. Cheers, David.

