Bugzilla – Bug 7917
Bridged setup difficult to achieve
Last modified: 2009-10-21 09:49:03 UTC
Setting up a bridged Jive seems to use the following menu structure (all from memory just now): ... / (3) Select wireless region / (4) select between (a) "connect using squeezebox" and (b) "connect using wireless network" (5.a) - select squeezebox (from list of SBRs found in setup mode) (5.b) - select from list of found networks or Other network Except that menu (4) only occurs if it has found any SBRs to setup. If not, it goes straight to 5.b. It seems pretty hit-and-miss as to whether it finds the SBR that is waiting to be setup I think this is the main problem. I think that this is the primary cause of my frustration whenever I have to resetup my bridged SBC. If, because it fails to find the SBR to setup, you break out of Setup and go to Settings / Advanced / Setupsqueezebox then it fails to setup the (wired) SBR. You get a message about not being able to connect your SBR to the network. I guess that this is not supposed to be a route by which you setup a bridged SBC but it could probably handle it better.
punting to 7.3
Ben can you look at this when you revisit the network settings.
this isn't going to be fixed by 7.3. retarget for 7.3.1
Changing target to next release
with only these exceptions, my bug list is being retargetted for 8.0 for 7.3.2 (very soon): https://bugs-archive.lyrion.org/show_bug.cgi?id=7186 Browse albums/artists/genres/ years should remember previous state for 7.3.3 (later, but before 8.0): https://bugs-archive.lyrion.org/show_bug.cgi?id=7139 Add editable "Network Settings" page https://bugs-archive.lyrion.org/show_bug.cgi?id=7502 Add setup mode to set Static IPs (even if DHCP is present) https://bugs-archive.lyrion.org/show_bug.cgi?id=7829 Jive menu broken if BLOCK_SIZE == list count + 1 and "Pla... https://bugs-archive.lyrion.org/show_bug.cgi?id=8878 Party Mode https://bugs-archive.lyrion.org/show_bug.cgi?id=10064 SqueezeCenter doesn't always auto-generate playerstatus w... (which will fix 8300) https://bugs-archive.lyrion.org/show_bug.cgi?id=6334 add applet for network diagnostics (currently assigned to Tom)
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code. Feel free to move it back if it's specific to the single original product.
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Felix: isn't this a dupe of another bug ?
This will probably be the same initially for Jive 7.4. We can talk about improving this later, so I move this to P2
Bridged setup is only offered if SBR has a wired connection, i.e. ethernet cable is attached. When SBR has a wired connection it boots up with a different SSID to signal SBC about that which in turn then offers to setup in bridged mode. Unfortunately the SSID cannot be changed later but only during a reboot. So for instance if SBR is factory reset and reboots without ethernet cable attached and goes into the red slow blinking and then an ethernet cable is attached it will not change the SSID and thus SBC is not offering bridged mode. I am not sure whether you saw this issue or another, but it would be good if you could retry with an ethernet cable attached to SBR and then do the factory reset or at least a reboot of SBR before trying to setup via SBC. You could also check the SSID SBR is using with a PC or Mac: SSID without ethernet plugged in: logitech-squeezebox-<mac> SSID with ethernet plugged in: logitech+squeezebox+<mac> Thanks
I do not think that a missing ethernet cable would have been the source of my previous problems. I have now reset both Ray & Jive three times and setup went smoothly each time. My suspicion is still that the problem occurs when Jive does not see the Ray at the critical moment in the setup process. I do not know if there have been any changes that would help with that. I guess you can close this if you cannot think of anywhere else to go with it. I do not know if this is ever a support issue.
Thanks for testing again, Alan. There were quite a few changes / fixes to make it work on 7.4 again, but I don't recall anything that would specially help this situation. I am going to close the bug for now. We can always reopen it if needed.
moving current p2 bugs to p3 to make room for moving p1.5 bugs to p2