On Tue, Jul 23, 2019 at 12:04 PM grumpy--- via Emc-users <emc-users@lists.sourceforge.net> wrote: > > On Tue, 23 Jul 2019, Mark Wendt wrote: > > > On Tue, Jul 23, 2019 at 11:45 AM Chris Albertson > > <albertson.ch...@gmail.com> wrote: > >> > >> 1) DHCP can in fact be "static". What you do is configure your DHCP > >> server to always assign the same IP to each physical device and/or make the > >> lease time really, really long. DHCP adds zero overhead once the IP > >> address and other info is set. > > > > What's the point? > > machines can be setup remotely > a new machine somewhere connects to the network > the sys admin adjust the dhcp settings > configuration is complete > any time a network setting changes it is push out to all machines
The argument was about the overhead of DHCP vs static IP addresses. Once a static IP address is configured into a machine, it no longer needs to renegotiate a DHCP lease. I was a system and network administrator for over 25 years as a DoD contractor. We would always do static IP addressing versus DHCP whenever we could. Much easier for DNS, lower network activity and less overhead on busy machines. With a hardwired network there is no real reason to use DHCP. DHCP is more useful for wireless networks where network nodes are constantly changing like at Starbucks. For network security alone, static IP addressing is much better. All sorts of reasons why static versus dynamic addressing is much better for defined networks. Mark _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
