Bug 1606 - Bridge Network feature
: Bridge Network feature
Status: RESOLVED WONTFIX
Product: SB 2/3
Classification: Unclassified
Component: SB Server
: 11
: PC Windows XP
: P2 enhancement (vote)
: Future
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-25 02:36 UTC by Dennis Floor
Modified: 2005-08-17 17:19 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Floor 2005-05-25 02:36:19 UTC
I've got two comments related to the bridge feature of the Squeezebox2.
1.: I've learned that the bridge function can only be activated when a device 
is connected to the ethernet port and this has to be done through the setup of 
the Squeezebox. Is it not possible to build this in to the "normal" 
operational menu?

2.: When the bridge function is activated, second device is connected (my 
laptop), Squeezebox is playing and it's working fine. But if I disconnect the 
second device (by removing the cable) the Squeezebox will lose his connection 
to the Slimserver (after some moments) and the screen will be blank (as it 
looks like it's not powered up).
When I try to switch on the Squeezebox it will try to connect to the server, 
but will fail. Reconnecting the second device will resolve or running through 
the Network setup of the Squeezebox again.

Info: Slimserver 6.0.2
    : firmware 11
    : Squeezebox2
    : Wifi connected (WEP128 + MAC)
    : Second device Laptop, connected through RJ45 (crosscable)
Comment 1 KDF 2005-05-25 03:26:30 UTC
item 2 is covered by bug 1302, and is fixed in the 6.1 nightly builds with the
firmeware included.

since 1 is an enhancement request ( i think ) changing status to enhancement.
Not sure how easy it is to change the port function after bootup (after setup)
Comment 2 Blackketter Dean 2005-08-17 17:19:01 UTC
The reason we left it out of the setup menu is because the vast majority of users aren't using this 
feature and it's an additional setup step (and a confusing one at that).  The workaround is simple, if you 
are going to use it as a bridge, plug in the device you'd like bridged.  (It remembers that you turned it 
on even if the player gets rebooted later...)  

Marking this one not to fix, reopen if you have a compelling example of why you'd need to have this 
option available when no device is plugged in.