On 01/22/2015 02:30 AM, Per Jessen wrote:
Anton Aylward wrote:
There are many situations where DHCP makes sense. An office with transient or 'hotelling' connections, an ISP, many others.
Running DHCP makes sense almost anywhere. It's obviously not required, but it makes life a lot easier. Just think a friend with an Android wanting to use your WiFi.
Contrariwise, there are many situations where static addresses make more sense such as DNS servers. I would generalize that to Infrastructure backbone components such as routers. DHCP is about DYNAMIC components. "Hotelling", workers coming and going; ISPs with clients that may or may not be there; freidnds with phones or tablets passing through. All good illustrations of TRANSIENTS. One idiom of the 'Net is "Cool URLs Don't Change". Yes that relies on DNS name mapping, but it also relies on the sites not changing their internal structure. The same can be said of "cool" addressees such as 8.8.8.8. Finally I'd like to make the observation that there are many security protocols that reply on IP addresses being constant. At a very basic level, even the SSH you use has that. If the IP address of the destination changes from one session to the next that comes up as warning since, in many cases, your record for that host in known_hosts might not match what DNS right now says. Then there's SSL/TSL. Surely, when browsing you’ve had a popup telling you that a site's certificate is invalid. Perhaps its out of date, but it may also be that certificate IP/name doesn't match. "Stolen certificate'? No. IP mismatch. Check with your ISP. There are going to be some services that they will only sell you if you have or make use of a static IP address. -- /"\ \ / 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