Bug 8186 - Squeezebox has wireless problems with Draytek Vigor 2930 VSn router (when mode 11n is enabled)
: Squeezebox has wireless problems with Draytek Vigor 2930 VSn router (when mod...
Status: RESOLVED DUPLICATE of bug 11193
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 88
: PC Ubuntu Linux
: -- major (vote)
: Investigating
Assigned To: Ross Levine
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-18 00:27 UTC by Igor Funa
Modified: 2009-03-31 15:49 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Funa 2008-05-18 00:27:39 UTC
I just upgraded SqueezeCenter to 7.0.1 (and Squeezebox firmware to 88) and now I can not reliably connect via wireless to my router & AP Draytek Vigor 2930 VSn. Before this upgrade it worked fine. 
You can hardly connect to the server, when you do it hardly responds to remote control commands, playback is impossible.
Wired connection works normally.
Comment 1 Igor Funa 2008-05-18 07:20:23 UTC
I have probably found what is causing the problem: 
Draytek Vigor 2930 VSn supports various wireless modes: 11b + 11g + 11n.
If you have enabled all these modes then there is a problem with Squeezebox.
If you disable the 11n mode (i.e. only 11b + 11g) then it works fine!

Well, this is just a temporary workaround. Wireless HW/SW SHOULD work fine with any device which supports either 11b or 11g, regardless of support for 11n.
This is my opinion.

I hope this will be a hint for developers to point them in the right direction.
Comment 2 James Richardson 2008-05-18 21:31:08 UTC
Igor, what firmware version do you have on installed on the Router?

Version 3.1.0 is the latest available: http://www.draytek.com/support/download/Vigor2930.

Comment 3 Igor Funa 2008-05-19 13:28:28 UTC
(In reply to comment #2)
> Igor, what firmware version do you have on installed on the Router?
> 
> Version 3.1.0 is the latest available:
> http://www.draytek.com/support/download/Vigor2930.
> 

It is the latest (3.1.0).
Comment 4 Igor Funa 2008-05-22 09:27:59 UTC
(In reply to comment #0)
> I just upgraded SqueezeCenter to 7.0.1 (and Squeezebox firmware to 88) and now
> I can not reliably connect via wireless to my router & AP Draytek Vigor 2930
> VSn. Before this upgrade it worked fine. 
> You can hardly connect to the server, when you do it hardly responds to remote
> control commands, playback is impossible.
> Wired connection works normally.
> 

(In reply to comment #1)
> I have probably found what is causing the problem: 
> Draytek Vigor 2930 VSn supports various wireless modes: 11b + 11g + 11n.
> If you have enabled all these modes then there is a problem with Squeezebox.
> If you disable the 11n mode (i.e. only 11b + 11g) then it works fine!
> 
> Well, this is just a temporary workaround. Wireless HW/SW SHOULD work fine with
> any device which supports either 11b or 11g, regardless of support for 11n.
> This is my opinion.
> 
> I hope this will be a hint for developers to point them in the right direction.
> 

Now it seems that the problem is not related to the 11n mode. I have played a little with my Draytek router and now SqueezeBox works fine only(!) in 11b + 11g + 11n mode. Very strange. Now I am confused. Before the upgrade (from 6.5.x) I had absolutely no problem connecting wireless to the same router. Now there is a problem but I am not 100% sure if this is the problem of Squeezebox. I hope others will report success or failure with wireless connection.
Comment 5 Chris Owens 2008-06-04 15:23:02 UTC
If additional users see this problem, or have additional info, please let us know and we can retarget this bug for a real release.
Comment 6 James Richardson 2008-10-02 07:37:46 UTC
Moving monitor bugs
Comment 7 Ross Levine 2009-02-26 16:20:49 UTC
Igor do you still see this? I just updated our Draytek Vigor2600G to the latest firmware, 2.5.9, works great!
Comment 8 Ross Levine 2009-02-27 16:33:56 UTC
See also bug 11193
Comment 9 James Richardson 2009-03-31 15:49:06 UTC

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