Bugzilla – Bug 11844
Ethernet detect fails after wireless detect fails
Last modified: 2009-10-05 14:25:35 UTC
Start with a working system using ethernet. Do setting->advanced->network->wireless Do the song and dance, but make sure it fails, eg wrong WEP key. Use the back icon, top left, to go all the way up the menu tree to "Choose network type". Select "Connect to Ethernet network". It will fail to detect the ethernet network and ask are you sure the ethernet cable is plugged in! Unplug the ethernet, plug it back in again. It will then detect the ethernet network. This unplug/plug should not be necessary.
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 original product.
It's more difficult to fix this bug as I initially thought. It's not just an incorrect message box, but the ethernet link status is reported incorrectly from the kernel to userland and lua.
Wild guess. Is this to do with having the same MAC address on both interfaces?
== Auto-comment from SVN commit #7436 to the jive repo by felix == == https://svn.slimdevices.com/jive?view=revision&revision=7436 == Bug: 11844 Description: Ethernet detect fails after wireless detect fails
== Auto-comment from SVN commit #7437 to the jive repo by felix == == https://svn.slimdevices.com/jive?view=revision&revision=7437 == Bug: 11844 Description: Ethernet detect fails after wireless detect fails
Turns out there is a case we are resetting the carrier / link flag even when there actually is a link. Fixed in r7437
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.