Bug 2816 - MAC addresses resetting on SB2/3
: MAC addresses resetting on SB2/3
Status: RESOLVED DUPLICATE of bug 2283
Product: SB 2/3
Classification: Unclassified
Component: Misc
: 28
: Macintosh All
: P1 major (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-12 16:22 UTC by Kevin Pearsall
Modified: 2008-12-18 11:38 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2006-01-12 16:22:35 UTC
We need to fix this.
Comment 1 Kevin Pearsall 2006-01-12 16:25:09 UTC
And no, before you ask, I know nothing about this and can't reproduce it...
Comment 2 Blackketter Dean 2006-01-12 18:21:32 UTC
Subject: Re:  MAC addresses resetting on SB2/3

Kevin:  please add details about the setups that folks have.  Access  
point info, network info, if the player crashed at all, etc....  We  
need to gather information here.

Comment 3 Adrian Keeling-Look 2006-01-13 06:35:08 UTC
Here's my set-up:

SB3 with v28 firmware.

Edimax EW7207APG Router (v0.19 firmware)
no encryption and not in enhanced mode
mac filtering was active

http://www.edimax.nl/html/english/products/EW-7207APg.htm

SlimServer 6.2.1 running on Mandriva 2006 with the following extra plugins:

 * AlienBBC v1.00a
 * Lyrics v0.5
 * Biography

Here's what happened:

I was playing AlienBBC on Radio 4 (v1.00a)

(player was left running as I was testing mplayer dev-CVS-20051220 to resolve garbling issues with the R4 stream)

Came back after a couple of hours to find screen blank.

Until then, my set-up worked fine from xmas onwards. 

Since my slimserver is currently running on my development box, I can't remember whether or not the server was reset/rebooted/crashed at any point (MDV2006 hasn't been that reliable on my dual Athlon system).

During the process of trying to work out what was wrong I upgraded the router firmware to v0.29 and switched of mac filtering.

Eventually worked out the mac address had been reset to ff f3 00 00 00 or was it 00 00 00 f3 ff (can't remember exactly now).

Once set back to the factory value, everything was okay.

Hope this helps.
Comment 4 Blackketter Dean 2006-01-28 11:01:17 UTC
BOUNTY!

We'll send a free Squeezebox 3 to the first person who can provide a way to reproduce this corruption issue.  Feel free to post your steps to reproduce here or email dean@slimdevices.com

Thanks.
Comment 5 Kevin Pearsall 2006-02-07 12:07:13 UTC
Regarding what hardware/etc folks are using, it's been everything.  Wireless, wired, I've had reports of people having this issue with just about every brand of router I can think of...

Often times it seems to be power related, though.  Like minor brownouts or the plug getting jiggled or something like that.
Comment 6 Kevin Pearsall 2006-03-02 15:27:46 UTC
That seemed to do the trick.  I don't have power surges, but I have had power loss recently (storm related).  I've also recently re-installed slimserver.  As for my network, here it goes:

SlimServer--crossover-->SB2-1(wireless bridge)--802.11g-->Belkin Pre-N MIMO Router--802.11g-->SB2-2

Does that help?
Comment 7 Kevin Pearsall 2006-03-02 15:28:11 UTC
(i'll just start pasting replies from my mac address reset canned reply)
Comment 8 Kevin Pearsall 2006-03-02 16:50:00 UTC
	We are currently running Slim Server version 6.1.1 with Player
Firmware version 1.15. I know there is a newer version for both (I'm
running that on the system in my house) but we have not upgraded these
since they are stable with the exception of this issue. I have seen and
corrected this issue on my test system and will be upgrading that to the
current version today to test.
Comment 9 Kevin Pearsall 2006-03-03 14:18:46 UTC
more information from another customer with a mac address reset:

We're not exactly sure why that happens yet, but could you possibly tell me more about your system and network setup, including what hardware is involved?  Have you had any power surges recently or anything like that?

Sure, you can ask me all the questions you want if this isn't enough.

I've had a squeezebox for a while:

Player Firmware Version: 28
The IP address for this player is: 192.168.0.101:17926
The ethernet MAC address for this player is: 00:04:20:ff:ff:01

It's connected by an ethernet cable to a D-Link DI-624 wireless hub/router.

The slimserver software runs on a Debian Linux box that's also wired in to the D-Link router:

phil@kenzo:~$ /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 00:10:DC:6A:DE:36
          inet addr:192.168.0.50  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:107155854 errors:0 dropped:0 overruns:0 frame:0
          TX packets:115692240 errors:0 dropped:0 overruns:0 carrier:0
          collisions:18260620 txqueuelen:1000
          RX bytes:3193687224 (2.9 GiB)  TX bytes:3742152290 (3.4 GiB)
          Interrupt:11 Base address:0xec00

I haven't had any power surges that I know about.

If the MAC address on your player needs to be set back to the original, you can do this by pressing and holding the left arrow on the remote until you get to the main setup menu.  From there, press right on view current settings, then press up until you see the MAC address.  Press right on the MAC address and it will let you change it back to the factory assigned one printed on the label on the bottom of the unit.

Ok.  All set.  Well, I don't have Squeezenetwork running yet, but I'm getting screens that I haven't hitherto been able to access before.  The MAC address on the bottom of the unit is 00 04 20 05 AC DE and it somehow was 00 04 20 FF FF 01 before I reverted it back.

Not sure if that helps you.

One comment: I googled for this information by searching for the errmsg string and didn't find instructions that worked for me.  It would good if you could make this information easier to find.

Thanks again for your help, though.  I'm very happy overall and recommend your product all the time.  One of my friends just bought one and he's happy too.
Comment 10 Kevin Pearsall 2006-03-04 17:41:35 UTC
The router is a D-link DI-614+ and static DHCP is enabled so that the same
IP address is assigned to specific MAC addresses. the current displayed
address on the SB is 00-04-20-09-01-01 and this matches with the IP address
assigned by the router. I do have to reboot the router occasionally for some
mysterious reason to get the network going, but there hasn't been any
electrical disturbance recently AFAIK.
Comment 11 Kevin Pearsall 2006-03-04 18:49:11 UTC
Thanks for your reply. Coincidentally, we did have what I believe to be a "sag" recently, however, I didn't notice anything unusual afterward.

My network setup is:

Comcast broadband cable
Toshiba PCX1100U modem
(1) Linksys WRT54G wireless G utilized as router/wireless/switch
Wireless channel 11- 2.462 GHz
WPA PSK encryption
(2) Linksys WRT54G utilized as a repeater/switch
Wireless channel 11- 2.462 GHz
WPA PSK encryption
Slimserver is running on a Windows Pro PC and is connected to the net via ethernet
1 GB memory
3.0 GHz Intel processor

I have two Slimdevices, one new version and one older version, both of which connect to the same Slimserver. My downstairs unit is connected via the Linksys repeater/switch via hard ethernet connection. The upstairs unit, which is the one with the MAC issue, is connected wirelessly. Typically, the signal strength varies between 45-55 %.
------------------
i think what he meant by sag is that he had a bit of a brownout...
Comment 12 Kevin Pearsall 2006-03-06 17:33:02 UTC
I do have a problem with blackouts and, in fact, lost the power supply in my other SB2 that never required the MAC reset. I replaced the PS and it has been fine ever since. 

The SB2 that lost the MAC address is powered via an external SLA battery that charges when "off".  I don't know when the address scrambled but I would guess that it is less likely that the scramble was related to the blackouts. 

Both units are wirelessly connected to the same D-link AP and have always been fine with local streaming.

Let me know if you need any more info
Comment 13 Kevin Pearsall 2006-03-07 14:18:27 UTC
* Windows XP Pro computer (2.56GB AMD Athlon, 1GB RAM, etc.) running Slim
Server 6.2.2
* Music library and playlists managed through iTunes 6.0.2.23 (Library
contains 8,582 songs, nearly all Apple Lossless files, with a few MP3s and
AACs)
* Two Squeezeboxen on the network (both wired), one original, one Squeezebox
2 (only running SqueezeNetwork/Pandora on the "2")
* Comcast broadband Internet
* Linksys home network, all hard-wired with Cat 5e cable.
* The Squeezebox 2 runs off of a Linksys 5-Port 10/100/1000 Gigabit switch,
as do (currently) an Xbox 360 and a second desktop computer.
* Both the analog and coax digital outputs of the Squeezebox 2 run into a
NAD T773 a/v receiver
* All of the audio equipment, including the Squeezebox 2, is powered through
a Belkin PureAV PF40 Power Conditioner/Surge Protector (but no, haven't had
any surges, blackouts or other power problems)

Have not had any other issues until the most recent Slim Server and
Squeezebox firmware upgrades to use the Pandora service.  Hope that helps.
Let me know if you need any other information.
Comment 14 Kevin Pearsall 2006-03-07 16:24:16 UTC
Seimens Speedstream 411 DSL modem
Netgear WGR614 v6 wireless router
Dell Inspiron 9300
I keep my mp3s in itunes.
 
No power surges as far as I know.  I had the MAC problem once before but it fixed itself.
The wireless router (or the router in combination with the modem) has been nothing but trouble since I got it.  Replacing the router (which I plan to do soon) may fix this problem among others.
Comment 15 Kevin Pearsall 2006-03-09 14:08:57 UTC
More notes from an affected user:
-----------------
This is the first time this has happened.  I wouldn't term myself a "power 
user".  The system gets used maybe 3 hours a day.	More on weekends.

Server is running on a Dell 1.4GHz P4, 1GB RAM, WinXP Home / up 24hrs a day 
/ Rebooted every 45 days on average.
Router is a Linksys WRT54G Ver. 1.0 running the latest firmware release from 
Linky (not third-party)  Rebooted once a year on average.
All connections are wired.
All hardware on UPS's.

I couldn't tell you when this happened as I only noticed it when we went to 
use SN.  As I said, our connection to our SlimServer with its local music 
and internet radio stations all worked fine.  I can tell you it happened 
with the 6.2.2 nightly from December.  There was no "cataclysmic event" that 
we can recall where the box locked up hard.  It just runs and runs.

I know this isn't much to go on.  These intermittent failures are the worst. 
Good luck.
Comment 16 Kevin Pearsall 2006-03-10 10:44:04 UTC
Thanks for the reply.  I found the MAC address resetting procedure on the
forum, followed it and the SB3 and SN are working fine now!

FYI, for your knowledge database:
Not aware of any recent power surges or black/brown outs
Dell P4 2Ghz CPU (XP Home) running SlimServer Version: 6.2.1 - 5194 -
Windows XP - EN - cp1252
Netgear Gigaswitch
Netgear Router
Cable broadband modem
SB3 wired
Infrant Ready NAS
Comment 17 Kevin Pearsall 2006-03-10 10:44:31 UTC
Many thanks for the response - I will try the reset once I am home this evening.
 
I have Slimserver 6.2 running on a iMac G5 with 10.4.? installed opertaing system.
 
The wireless network uses Dlink Routers.
 
As regards power surges I do not think so as the power does not tend to have those issues.
 
If you need more detail let me know and I will send it through to you.
 
The only other activity I have undertaken with the Squeezebox recently is to try and install AlienBBC - Got the stream to work on my iMac and for the plugin menu to show on my Squeezebox, even to extent of it trying to connect to BBC but no sound comes form the unit - (Doubt it is related and have tried to solve issue via forum but to no avail at present)
Comment 18 Blackketter Dean 2006-04-21 20:06:30 UTC
Chris: a long standing and, so far, difficult to reproduce bug.
Comment 19 Chris Owens 2006-04-25 11:09:00 UTC
Will try to track this one down
Comment 20 Marc Auslander 2006-06-02 15:03:40 UTC
00:04:20:06:3E:0A changed to ffecfafffff9
other settings lost
was playing a 1400kbs wav file. stopped with display overlayed with clutter.  was still connected and seemed to respond to remote but settings were lost at restart.
Comment 21 Marc Auslander 2006-06-02 15:09:30 UTC
(In reply to comment #20)
> 00:04:20:06:3E:0A changed to ffecfafffff9
> other settings lost
> was playing a 1400kbs wav file. stopped with display overlayed with clutter. 
> was still connected and seemed to respond to remote but settings were lost at
> restart.
> 

Sorry I left out the facts.

Recent 6.3 build, firmware 50, SB3, linksys wrt54G V2 wireless
Comment 22 Chris Owens 2006-06-05 11:40:36 UTC
Marc, could I persuade you to attach the wav file to this bug for me to look at? :)
Comment 23 Marc Auslander 2006-06-05 13:32:30 UTC
I have saved the wav file.   But I've also tried to reproduce the failure a number of times with no success - so its not a straight forward property of the file.  And the file is 630megs - so I don't thing you want me to attach it :-).

If you really want it of course, I'll try to get it to you.  Instruct me.
Comment 24 Chris Owens 2006-06-05 13:58:02 UTC
Okay okay I retract my request, although I probably should add a few giant files to my test suite. :)
Comment 25 Blackketter Dean 2006-06-20 11:27:35 UTC

*** This bug has been marked as a duplicate of 2283 ***