On 04/01/2016 08:46 AM, Dave Howorth wrote:
On 2016-04-01 16:34, Anton Aylward wrote:
On 04/01/2016 11:12 AM, Dave Howorth wrote:
Yes, it's a home system. A few PCs and a printer and a couple of TV boxes and several phones and a couple of mobile computers, plus whatever visitors bring. Connected to several switches connected to the router.
Sounds like my system, minus the TV.
There really is no reason to use DHCP in something that simple. You're NOT hotelling a laptop that is going to be connected to different sites. You're not dealing with a phone or tablet connecting via wifi, that also might connect, again by wifi, to different sites. The latter specifically don't need, can't have, permanently assigned IP addresses.
The hard-wired, PERMANENTLY connected devices can.
THAT is the simplest, and also the most robust, network configuration.
That's what I used to do, but maintaining the files on all the machines is tiresome. So once we switched to DHCP at work, I switched to it at home as well. Only one device to manage seems to work for me.
There's a misconception there. The real issue isn't the assignment of addresses, its the mapping of names to IP addresses, which is a DNS issue not a DHCP issue. You are not starved for IP addresses. handing out the mapping is what demands maintain the /etc/hosts files on each machine and yes it is tiresome. The whole point of DNS is to avoid that.
Late model DNS integrates with DHCP, so the DHCP server issues a dynamic update to the late model DNS server. That's the setup at your work, in all probability. Its overkill for the home setup you and I have at home. I've experimented with it in the past, implemented it in a couple of different ways at client sites. If everything is static, or for the parts that are static, DHCP makes no sense. Hard wire the machine, hard wire the addresses and hard wire the entries in the DNS service.
I confess I haven't looked into how it all works too closely. I set the hostname on each machine (for that machine, not for every machine) or use whatever the machine decides if it's vaguely sensible, and then somehow the router does the rest. I don't set up a DNS server. How come on a Windows system when it's set up for DHCP (wireless or wired) there is no delay, but with openSUSE wicked hangs on systemd startup? I have noticed this too; it says something like "A start job is running for wicked" and just hangs there...this should not happen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org