Opened 5 years ago

Closed 17 months ago

#655 closed (fixed)

wireless N settings not appearing in Mixed mode

Reported by: Bronsen Owned by: somebody
Keywords: Cc:

Description

I'm not sure if this is a Defect or if it was intentional. Under Wireless>> General Tab on a WRT350N when Wireless network mode is on Mixed no settings for wireless N show up. I'm attaching a Image to show you what I mean. in order for wireless N to work properly in mixed mode I have to set to N-only and then set to what I want but everything is set to auto upon applying settings. When I switch it back to Mixed mode it holds but it will jump channels even if I select a channel. then it will revert back to 20mhz only and not 20 and 40. I know that the original Linksys Firmware alows both narrow and Wide Channel to coexist. When in Mixed mode. Thank you for looking at this issue.

Attachments (4)

wirelessmixed.JPG (75.7 KB) - added by Bronsen 5 years ago.
this is the settings tab when in mixed mode.
wirelessNonly.JPG (75.6 KB) - added by Bronsen 5 years ago.
this is the settings tab when in N-Only mode.
utilityshowing20and40.JPG (46.0 KB) - added by Bronsen 5 years ago.
utility showing 20 and 40 mhz when in N-Only it will also hold the settings over after setting to mixed mode until reboot.
utilityafter setting back to mixed.JPG (45.7 KB) - added by Bronsen 5 years ago.
mixed mode after setting channel to 1 for some times it will broadcast on channel 6 and not 1 and my wireless card will broadcast on 1 and only connect at 1.0 mbps I thought it was driver issue with card but have tried several of them.

Download all attachments as: .zip

Change History (9)

Changed 5 years ago by Bronsen

this is the settings tab when in mixed mode.

Changed 5 years ago by Bronsen

this is the settings tab when in N-Only mode.

Changed 5 years ago by Bronsen

utility showing 20 and 40 mhz when in N-Only it will also hold the settings over after setting to mixed mode until reboot.

Changed 5 years ago by Bronsen

mixed mode after setting channel to 1 for some times it will broadcast on channel 6 and not 1 and my wireless card will broadcast on 1 and only connect at 1.0 mbps I thought it was driver issue with card but have tried several of them.

comment:1 Changed 5 years ago by Bronsen

These Issues have existed since the support of the 350n was added to v24. though I have noticed one fix when in N-Only mode the speed issue has been resolved.

comment:2 follow-up: Changed 5 years ago by malmo

  • Resolution set to worksforme
  • Status changed from new to closed

The b,g-mode use 20Mhz channel wide and n-mode use both 20Mhz and 40Mhz wide channels. But only under 40Mhz wide you get 270Mbit. You can't mix channel wide. So under mixed you will get b,g,n-mode with 20Mhz wide, getting n-mode 20Mhz max ->130Mbit

comment:3 in reply to: ↑ 2 Changed 5 years ago by Bronsen

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Replying to malmo:

The b,g-mode use 20Mhz channel wide and n-mode use both 20Mhz and 40Mhz wide channels. But only under 40Mhz wide you get 270Mbit. You can't mix channel wide. So under mixed you will get b,g,n-mode with 20Mhz wide, getting n-mode 20Mhz max ->130Mbit

Doesn't work if it was working then in mixed mode you'd have both 20 and 40 mhz only 20 mhz is working look at the original linksys firmware which I did check against I set it to N-mode only works fine set it to mix mode only 20 mhz check it out it should be able to work together just like the linksys firmware. Mixed mode in linksys firmware I get both 20 and 40 mhz and my N and G work fine together. I did notice one thing is that they are on 2 different channels maybe you should look at yours closely I get 270 mbit with linksys and only 104 mbit with DD-Wrt. I've been using DD-wrt since V22 days before that is was $vea$oft I couldn't justify paying for support that didn't exist with $vea$oft. And I still say that only admin's should be able to close tickets.

comment:4 Changed 3 years ago by anonymous

  • milestone v24 final deleted

Milestone v24 final deleted

comment:5 Changed 17 months ago by LOM

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.