Maybe I spoke too soon - Got Controller, got problems

[egd]

I thought I saw someone with a Netgear, but people don't always bother to mention their network gear when discussing Controller issues. You and I are the only people to have specifically quoted Sveasoft that I can tell, although a new G-Dude just reported a problem with a Linksys WRT54GS but doesn't mention the firmware.

If it's of any use I'm running a Netgear WG102 WAP on firmware V4.0.27. The Controller and (to a lesser extent) the Receiver are the only devices that have connection issues, sometimes struggling to connect (Receiver) and often losing connectivity (Controller). My SB3s, mobile, PDA, laptop and iPod Touch are all rock solid connecting via same device and the SB3s stream FLAC without any issues.

[slydog75]

If it's of any use I'm running a Netgear WG102 WAP on firmware V4.0.27. The Controller and (to a lesser extent) the Receiver are the only devices that have connection issues, sometimes struggling to connect (Receiver) and often losing connectivity (Controller). My SB3s, mobile, PDA, laptop and iPod Touch are all rock solid connecting via same device and the SB3s stream FLAC without any issues.

That sounds like a weak signal problem. How many bars are on your controller? That's (IMO) the worst issue with the controllers, they have a horrible range compared to any other devices.

However, it doesn't sound like it's the same issue we're discussing in this thread, where the controller completely refuses to EVER connect to a server even with 100% signal strength.

[egd]

That sounds like a weak signal problem. How many bars are on your controller? That's (IMO) the worst issue with the controllers, they have a horrible range compared to any other devices.

Heh, I can have this issue with the Controller and Receiver in the same 20SQM bedroom as the WAP.

[Mark Lanctot]

Why is the decision between Tomato and Sveasoft?

I had a beta controller and a production controller both running fine with a WRT54G with DD-WRT firmware.

[Milhouse]

Why is the decision between Tomato and Sveasoft?

I had a beta controller and a production controller both running fine with a WRT54G with DD-WRT firmware.

I would like to get to the bottom of the problem with the Sveasoft firmware which works perfectly with every other wireless device I have. Identifying the "problem" with Sveasoft firmware may also be of benefit to other non-WRT54G(S) owners who are also experiencing similar problems. I firmly believe the Controller is doing something weird and it's not only WRT54GS/Sveasoft routers that have a problem.

In pretty much all respects the wireless connection between the Controller and my Sveasoft router is solid, it's SqueezeCenter that is rejecting Controller requests for some unknown reason.

Switching to DD-WRT may be a solution, but it's really more of a workaround. If the problem I have can be identified beyond all doubt as a flaw in the Sveasoft firmware (currently it's only an assumption) then I would switch away from Sveasoft, until then I have my doubts and would like to help find a solution if possible. I know when people had WiFi problems with Nokia tablets, the Nokia WiFi developers made an effort to buy the routers and replicate the problem - it wouldn't be hard for Slim Devices to do that, or even just show some interest/concern in these problems on the forum.