On 08/11/2019 03:36 PM, Dave Howorth wrote:
Your experience differs from mine then. Most devices (all, IIRC) that I attach to my network get an IP4 address by sending a DHCP request which is answered by my router. I can then discover what address has been assigned by looking at the router's web page, and change it or assign it a static address if I desire.
I believe some of the recent IoT devices can also be told to configure themselves to present a wireless AP, which you then connect to with a phone or whatever and tell it about your local environment. You then reboot it and it connects to your network.
I haven't ever come across any device that comes up with a fixed address, except for routers which always do IME, and usually but not always as 192.168.1.1. The Fritz!Box comes up as 192.168.178.1 initially, for example.
(side note:...) This is why I have always configured a local server for each LAN running ISC dhcpd and bind with dhcp providing dynamic updates to bind. dhcpd is incredibly flexible handling MAC based fixed IP handout or a generic addresses from a range of IPs it hands out on request otherwise. (it has gotten much more capable, but my use of it hasn't changed in a number of years which just barely scratches the surface using simple TSIG auth for zone updates, etc..) It also lets me handle the whole process one-step removed from my router on the LAN side which I've liked for security reasons given the questionable security built into consumer grade routers, etc.. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org