On 01/21/2015 03:38 PM, John Andersen wrote:
Permanently is relative for things electric.
Indeed. The address has outlived a couple of machines :-)
But even if it was, so what? Renewing an IP presents no disruption, no load on your network, and, if you are doing it even halfway right will result in the SAME IP every time. Mac Address Reservations.....
And having permanent addresses represents even less of a load ... (Now lets see who can piss higher up the wall....)
That is not simple as best I can tell. (I mean its fine if its JUST you that has to reference some device by name/IP
Yes, I said that. Just me. Home system. I also qualified that with saying that there were many situations where DHCP makes sense. I'm saying that in my case for my BACKBONE it doesn’t. Please note all the qualifications I've mentioned. You seem to be ignoring them.
but when there are 5 computers in the house plus 12 portable devices, it becomes unworkable).
Of course its unworkable! Yes there are five static devices on the BACKBONE switch. Two of them are secondary routers, both LinkedSys. As I said. A voip/ANA and Wifi. As I said, both of those hhave DHCP downstream. But LinkedSys is not friendly, this is not all some single Linux box running dnsmasq with integrated DNS naming and DHCP.
I tried Statics. Its a total mess, especially with coming and going devices in the house like tablets laptops and cell phones.
I've run household, office and ISP/Service and know where DHCP is applicable. And not. It is rarely applicable for BACKBONES. Key example: my gateway is statically assigned, always .1. Ditto other key items. Yes, they could be MAC linked on the DHCP, but when things go wrong and you need to do some network debugging, having fixed addresses for key components like the Router, the SAN, other Gateways is so incredibly convenient. Whatever device is the DHCP server, it could have failed. Setting up permanent addresses for BACKBONE devices is not difficult.
True, any competent DHCP server can work around "usurped" static IPs, but this can cause all manor of problems depending on boot-up order.
In something like 30+ years of networking I've never had a problem with that. Usually because I do SOMETHING LIKE reserve the first 15 or so addresses of a "class C' sub-net and don't even begin the DHCP pool until .32. As far as I can tell its a matter of discipline. I set up a discipline for doing this after considering the complications and possible errors and failures modes and have stck with it and as a result hav't had problems.
If you have to have a static, put them all together in a range, and tell the DHCP server not to use that range. But in the 15 years since I abandoned Statics, I've seen only one convincing case for use of a static, and that is for the internal IP of my main server which is also my gateway.
As I say, I've been doing that, PLUS, for a long while. The PLUS is to simplify debugging when things fail. As they sometimes do. Call me a "belt and braces" type of old fogie ... Again: do read my earlier post. I run a multi level network. I do use DHCP. Just not on the BACKBONE. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org