Bugzilla – Bug 4538
Easier setup: re-think Auto-IP
Last modified: 2010-05-07 10:20:14 UTC
Our current Auto-IP implementation has good intentions, but can easily mislead the user into a very confusing situation where they think they have successfully connected to the network, but they are unable to find a SlimServer. It makes it appear that the SlimServer is not running, when in fact the problem is that Squeezebox has failed to connect to the LAN for some reason. There are only two situations where Auto-IP is desirable: 1) We are connected by crossover cable directly to a an un-configured ethernet port 2) We are connected to an Ad-hoc wireless network The problem is that we offer Auto-IP in any situation where DHCP fails, and we consider the choice of Auto-IP to be an unconditionally successful connection. Furthermore, novice users do not know what it means to "Self assign an IP address" so this is a befuddling menu just in itself. Therefore, I suggest the following changes to Auto-IP logic: 1) Only consider Auto-IP successful if it allows us to locate at least one SlimServer 2) For basic setup, do NOT prompt the user for Auto-IP. Choose it automatically if DHCP fails but Auto-IP is successful (by this new definition of success). 3) For advanced setup, we will suppose that the user knows what Auto-IP is, and will only choose it if he really wants it. Do NOT fall back to Auto-IP automatically. Make it a third option after DHCP and Static.
We don't do Auto-IP during setup unless the user chooses to, and only after DHCP has timed out after 30 seconds. Additionally, if the DHCP server comes online after the user does choose to self-asssign an IP address, it will automatically use the DHCP obtained address.
All new Squeezebox products are likely to be based on the SqueezePlay platform. We do not plan to implement any further enhancements to the ip3k firmware or which are targeted specifically at ip3k-based products.