joncourage wrote: > Also, device IP address conflicts can be a tricky bitch to suss out, > and manually setting addresses rather than allowing DHCP to deal with > it causes this type of problem with some regularity (I've had times I'd > swear on my life that addressing was good only to discover later I was > wrong).
This is often more than just tricky to find. Fixing it is usually trivial DHCP (and its precursors) were invented because fixed IP addresses are essentially unmanageable once the number of computers gets "large" > DHCP can also foul up, and I'm not sure the DHCP servers sitting in a > $60 WAP or internet router are going to be the most consistent for > correct addressing. I run two DHCP servers in my house, with the servers assigning fixed TCP/IP addresses by MAC, and my SqueezeBoxen (and laptops with wired and wireless) having two separate mappings. With this, I have had zero problems in ages, except when (and not if, but when) I get the two dhcpd.conf files out of sync. I believe that IPv6 was going to fix this about a decade ago. -- Pat http://www.pfarrell.com/music/slimserver/slimsoftware.html _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
