Re: Apple Airport Express + DSP
IMHO, static IPs are a nightmare. Maybe in an install situation where nothing will ever change, sure, it might work. But for any gig where a replacement device might need to be brought in, a device would need to be reset, etc, it is a recipe for disaster.
Why?
Because setting a static IP is more than setting the IP, it requires setting the subnet. Sure, everything should be on 255.255.255.0, but will it default to that? Are you going to rely on your guys knowing that at a show when there's an emergency? Are you really going to keep an IP address table handy so you know what to assign that new fancy device to? What if you don't have a list of what's what, and you need to readdress something quickly. Heck, what if you get in a loaner device that is set static and it's not labeled? Now you have to reset the device, check the manual to see what it defaults to, change your computer's static IP to be one in the range of your new static device, change the static device, then change the computer back.
Trust me guys, static IPs are NOT recommended for anything that could change, especially in a time-crunch situation, where the people doing the changing might not have network experience.
Edit: more along the lines of this thread, trying to work around a device that doesn't support DHCP is a waste of time. Throw it out, buy a $50 wireless N router, and call it a day. I do realize there are some devices that have to be static, like Yamaha consoles (I think?). At least the iLive supports DHCP...