Bugzilla – Bug 15389
Alarm -- Backup requested from wrong IP on dual-homed host
Last modified: 2011-11-06 23:24:21 UTC
Created attachment 6411 [details] Image of Radio during alarm failure When the alarm set does not properly play and the Radio goes to the server for the "backup alarm" sound, it may request from the "wrong" IP address when the SlimServer has more than one active interface. When this occurs, the message "Connection reset by local host" appears and no alarm sounds. As the alarm does not sound, I consider this a "critical" bug. Dual-homed hosts can and will occur "in the wild" under various conditions including, for example, when the Internet connection is being provided over an Ethernet connection and is being "shared" over the WiFi card. The conditions in particular here involve a Mac 10.5.8, Perl 5.8.8, Squeezebox Server 7.4.1 r28947, that generally connects through the 192.168.6.x network on the Ethernet card and connects through WiFi to the 192.168.132.x network (where the SqueezeBoxes reside). As can be seen in the attachment, it is trying to retrieve the file from the wired interface (192.168.6.5), not the wireless interface (192.168.132.13) through which it reaches the sever. Version: 7.4.1 - r28947 @ Tue Oct 20 08:13:22 PDT 2009 Hostname: port5.--omitted-for-privacy--.com Server IP Address: 192.168.6.5 Server HTTP Port Number: 9000 Operating system: Mac OS X 10.5.8 - EN - utf8 Platform Architecture: x86 Perl Version: 5.8.8 - darwin-thread-multi-2level MySQL Version: 5.0.22-standard Total Players Recognized: 3 Player Model: squeezebox3 Firmware: 130 Player IP Address: 192.168.132.14 Player MAC Address: 00:04:20:06:35:42 Wireless Signal Strength: 78% Player Model: squeezebox3 Firmware: 130 Player IP Address: 192.168.132.15 Player MAC Address: 00:04:20:06:33:fd Wireless Signal Strength: 53% Player Model: baby Firmware: 7.4.1-r7915 Player IP Address: 192.168.132.211 Player MAC Address: 00:04:20:26:7e:96 Wireless Signal Strength: 70% port5:jeff jeff$ netstat -anf inet | fgrep 9000 tcp4 0 0 127.0.0.1.9000 127.0.0.1.64088 ESTABLISHED tcp4 0 0 127.0.0.1.64088 127.0.0.1.9000 ESTABLISHED tcp4 0 0 192.168.132.13.9000 192.168.132.211.49853 ESTABLISHED tcp4 0 0 *.9000 *.* LISTEN The above confirms that the server is properly listening on all interfaces and that the Radio is connecting through the 192.168.132.13 (WiFi) interface.
There is definitely a change in 7.4.2 that makes certain the 'backup' alarm sounds. I am hesitant to make risky changes in a version that is close to release. I feel like SC with multiple interfaces (and IP addresses) is not going to affect many users.
Andy notes that there's a workaround that you can pass in http_addr to specify which address to listen on.
Unassigned bugs cannot have a priority.