On Wed, 02 Mar 2005 14:00:36 -0800, Phil Karn <[EMAIL PROTECTED]> wrote:
> > The best way is to assign a fixed, static IP address to each host on > your own local network. There's really no point in allocating IP > addresses dynamically to your own hosts given that you have such an > abundant supply of 192.168.0.xxx addresses. Dynamic assignment also > makes it difficult for your hosts to find and talk to each other (unless > they use Apple's Rendezvous). However, it's still useful to keep DHCP > and dynamic addressing around for the benefit of guests with laptops, so > you don't really want to turn it off entirely. The problem is a mis configuration of the dhcp server. It should not have been assigning IP's in the same range that some are manually set. .1 is my router. I reserver .2 through .10 for utility purposes (print server, local yum server, dmz machine, caching name server, etc. - some of those are actually same box, but done through multihoming so I can seperate them in future if I need to) 11 through 99 I reserve for static IP's when needed. When something requests an IP - it gets one from the 100 to 149 range - 50 dhcp addresses are far far far more than I'll ever use. 150 through 254 I just do not use, and probably never will. But that was the problem - something was assinged an IP address that was in use in the static range. My squeezebox will most certainly be dhcp, it has no need to be static. My slimserver currently is on my main box (.11) but is likely in the near future to be moved to a shuttle, where it will get a utility IP address. Using dhcp is fine as long as you have no need to talk to the box from another, and as long as your static IP's are not in the range the dhcp server controls. -- http://mpeters.us/ _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
