Bugzilla – Bug 1430
Squeezebox changes MAC adress after power switches
Last modified: 2009-09-08 09:25:05 UTC
Hi there, I have my squeezbox2 power supply connected to my amplyfier, so that the Squeezebox will be switched togwther with the amplifyer. When testing the remote control for the amplifier, I switched th epower several times - and suddenly the Squeezebox did not connect to the wireless lan anymore. When checking all settings, I noted that the Reported MAC address did change to a new value - after entering that into my wireless lan access table, everything worked fine. So for me th eproblem is solved - however, a network adapter shold not easily change its settings (makes life very hard if the internal settings do not match the externally stated data. Any ideas? Kind regards - Timmo
Wow, I never heard of this before. What were the two MAC addresses (the original and the new)?
what values have been seen?
Hi, the original Address (printed on the box) was 00:04:20:05:A6:63. the new address is (as displayed in the setting menu) is 00:04:20:09:01:01. serial no is230DFFA Firmware version 9 The box worked before and after the change - with exactly these adresses (I have configured access control at my wireless access point). All the best - Timmo
the :09:01:01 address is used in factory testing. The only way that we know to get it into that state is to press 2 while powering on. Is it possible that you did that? You do have the option of editing the MAC address back to its original (right from View Current Settings -> MAC Address).
I had the same behavior occur with my Squeezebox2. The power was cycled a few times within a few second period (I didn't shove it in completely back in the stereo cabinet), and it came up with the factory MAC. The remote wasn't even near me so 2 was not pressed.
Dean, any confirmation that FW16 has fixed this?
There weren't changes that would have made a difference on this.
Firmware 17 should address this issue. Timmo: Can you update to the latest nightly build tomorrow and see if you can recreate the problem? If so, please reopen the bug. If not, please mark it as closed. Thanks!