Bugzilla – Bug 6252
Setup fails in bridged mode when no DHCP server available
Last modified: 2009-09-08 09:13:07 UTC
Setting up a Ray and Jive using the "Bridged" configuration with Ray wired to the network, if Ray is unable to get DHCP, setup fails. Steps to reproduce: Connect Ray in setup mode via Ethernet to your network, I used a Mac sharing Internet over Ethernet, see bug 15 Select "Connect using Squeezebox" when configuring Ray from Jive Select MAC of Ray Notice Ray's led goes to Green then Blue however Jive will error with "Problem Connecting" with the only option to "Try again" or "Skip this step" with neither really working. I think what should happen is that Ray should stop at green and Jive should give the option to use a self assigned or static address when DHCP fails. I think this is the behavior I have seen when setting up the "Bridged" configuration over WiFi.
I just tried this at home connecting my Comcast cable modem directly to the Ray via Ethernet and got the same exact behavior.
Adding CC to the bug.
Created attachment 2486 [details] Three captures of Ray trying to connect to a Macintosh over Ethernet
Related to bug 15 which has to do with incompatible DHCP server. Bridge mode requires a working DHCP server.
Bug 6393 seems to be related since ray self assigns an IP. Following the workaround in bug 6393 does allow this setup to function with limited capacity since there will not be access to the internet when using self assigned IP.
Felix: do you expect to fix this for 7.0?
I intend to work on it shortly, but I don't expect it to be easy to find and fix and QA also needs to test it first. So, no, I don't think it will be in 7.0
Steven to re-test and update with new findings.
This bug is still valid running Duet bridged and no DHCP server is running or can be found on the network. Bug 15 being fixed does lower the possibility of someone encountering this bug however. Dean mentioned in comment #4 that bridge mode requires a working DHCP server, so would this now be an enhancement request? Even if that is the case I think there should be an indication on ray when it is using a self assigned address before it is connected to the server. Perhaps blinking blue as opposed to solid blue?
Assigning to Dean for comments.
Dan: Can you weigh in here? How often do you get a support issue for users who use bridged and don't have a working DHCP server?
This seems unlikely to get done for 7.0.1; retargeting.
I can't speak to the exact number we've seen of this fringe case. I filed bug 7502 due to customer feedback, but that was for Standard Wired mode, really. Julius reports he had one customer who wanted Bridged Mode with Static IPs. That's the only specific case of this I've heard of. (have not heard from Anoop or Osama on this, though.)
Please vote, comment, and re-open if you'd like us to pay attention to it in the future.
We continue to get customers asking for this feature to be available. After speaking with Felix, he agrees that we should fix this feature. Re-opening bug for closer investigation.
This connection method is also documented in our User Manual, making it more important to make work, IMO.
Our user guide says that things work without a DHCP server?
Felix: please prioritize and target appropriately
This is for bridge mode (Controller -> ad hoc -> receiver -> ethernet -> computer) when there is no DHCP server. The controller is not prompting for autoip/static.
Duet user guide indeed has a section 'How to use Static IP addresses with Squeezebox Duet' in the troubleshooting section. (At least it does not explicitly say one should use bridged mode.) I have no idea why SBC would not prompt for a static ip address in bridged mode when no DHCP server is available as in standard wireless mode it does.
Changing target to next release
Punting to next release
Targeting based on engineering discussion