Wireless Problem

[seanadams]

>
> want mine? It will save me the trouble of running it over with my
> car... Seriously, the MR814v2 that I have is junk, very prone to
> crashing.

Hmmm, the symptoms John reported are 100% consistent with the router
simply crashing - there's not much we can do about that.

When you're just using a router for accessing the web, if the router
crashes you just hit reload a few times until the page comes through -
it's hard to tell whose fault it is. When you're playing music, it's a
lot more obvious when the network goes down!

[Ken Gray]

Sean Adams wrote:
>>>
>> Updated firmware did not fix the problem. My access point is a Netgear
>> MR814v2 that has no problems with other devices.
>
>
> No ideas OTOH - we will need to get one and do some tests.
>
>>
>> Among the weirdness I've noticed is that I can't seem to find the
>> wireless nic's MAC address. The sticker on the back only lists one MAC
>> address. Is this correct?
>
>
> Yes. Squeezebox2 shares one MAC address between the wired and wireless
> interfaces. The dual MAC addresses on Squeezebox1 turned out to be
> unnecessary.
>
>>
>> Does anybody think that getting 802.11g access point would help?
>
>
> Yes, but we still want to fix whatever's wrong with the MR814v2. That
> may take us a little while if it's no longer in production, or not
> readily available.
>

I have a Linksys WET11 802.11b wireless bridge connected to my wired
network that worked fine with SB1. SB2 would see a good strong signal
from the WET11, but it wouldn't connect -- neither with WEP-128 nor with
encryption disabled.

The bridge has firmware V1.54, the latest, and I'm running server 6.0.0
on a RH8 box.

I replaced the bridge with a Linksys WRT54G, an 802.11g broadband
router, basically just using it as an AP. All is copacetic now.

Ken

[vidurapparao]

Sean Adams wrote:

> ....
>
>>
>> Does anybody think that getting 802.11g access point would help?
>
>
> Yes, but we still want to fix whatever's wrong with the MR814v2. That
> may take us a little while if it's no longer in production, or not
> readily available.
>
Actually, we do have a MR814v2 and the latest firmware (v.9) is able to
connect to it. I've tested both with and without WEP.

--Vidur

[John Rakestraw]

Dan Sully wrote:
>
> John - can you make sure that you don't have bitrate limiting turned on?
>
> It will be under your Player Settings -> Audio, and down at the bottom.

Oops, I meant to say this. Bitrate limiting is set to "no limit." And
I'm using 128 bit WEP.

From Sean:

> Hmmm, the symptoms John reported are 100% consistent with the router simply crashing - there's not much we can do about that.

The SB1 has worked (and continues to work) just fine with this router. I
don't think it's crashing.

-John

[Mike Arrison]

On Apr 05 18:36, Sean Adams wrote:
> >>
> >Updated firmware did not fix the problem. My access point is a Netgear
> >MR814v2 that has no problems with other devices.
>
> No ideas OTOH - we will need to get one and do some tests.

RESOLVED: MR814v2 now works. I didn't realize that a firmware upgrade
was dependent on the server version. I had been running slimserver 6.0
and when I updated the firmware (by holding "brightness"), I got no
change. But this morning I upgraded to 6.0.1 and THEN updated the
firmware, and that fixed it.

Thanks for the help.

-Mike Arrison