Posted: Sun Sep 20, 2009 6:02 Post subject: Bridged wrt600n will not run at N Speeds on 5GHz radio
So I have two 600n
the 2.4 ghz radio is set as G only and is for wireless clients. The 5Ghz radio links the two together.
At one point in time I thought it was running at 270. but when I look at it now it wont pass 54Mbit. Ive tried channel width, mixed, NA-only and it still wont communicate with the bridge at 270...Any ideas.
Try these advanced settings on the 5Ghz band.
I use channel 60 Upper 40Mhz and your security should be WPA2-AES, also you should turn your ACK timing = 0. Here are some other settings for the Advanced Wireless settings you can try:
Now go to Administration Tab and change these settings:
IP Filtering Settings
Max ports=4096
TCP and UDP Timeouts to 90 _________________ R7000 Kong vpn 23550-R01 (Main Router)
WRT610Nv2 converted E3000 vpnKong 21661 (RB)
WRT600N v1.1 BS std-nokaid 13637(5Ghz CB)(2.4Ghz AP)
WRT54G v5 BS micro 14684(RB)
Channel 60 - Done
Upper 40 - Done
WPA2-AES - Was already running
ACK 0 - Was already there
CTS - Auto (there is no Enable)
Framebust - Disabled (Was enabled)
Beacon 100 - Was already there
Preamble Auto - Was set to long
Afterburner Disabled - was already there
TX 71 - Was already there
WMM - Already enabled
IP Filtering settings were already configured as such
I also changed the bridge's applicable settings
Same results...Intresting what I do see is that if I look at the status page On the router it shows channels
60-62 @ 81 Mbps now (flucuates between 54 and 81)
Looking at the bridge it only shows channel 62
As a General rule I also disable ssid broadcast...but i renabled it....It had no effect
I also just tried newd vs newd-2, hardreset in between...didnt make a difference...this used to work fine.
Be aware that 270Mbit/s is the theoretical throughput under perfect to near perfect conditions. Don't expect the best. I don't get any better than an average of 100Mbps, and I'm about 3 feet from the router. _________________ Click here for Eko beta Click here for Brainslayer beta >>>PEACOCK THREAD!<<<
I do NOT offer personal assistance.
Please do not PM me for help.
Like I said, just because it can run at 270Mbps, don't mean it will. The A band, at 5 to 5.8GHz, is more likely to suffer from attenuation than B/G. Higher frequencies are more easily absorbed and blocked by materials that present less of a obstacle to lower frequencies. _________________ Click here for Eko beta Click here for Brainslayer beta >>>PEACOCK THREAD!<<<
I do NOT offer personal assistance.
Please do not PM me for help.
The 270 connection that you see in status is a theorietical maximum that is a reflection of the signal quality and has nothing to do with actual throughput. It really doesn't mean a lot. It only reflects the speed that the signal quality could support, which is meaningless if you are trying to connect wireless clients through a bridged router where the actual speed will be well below half what is reported in that screen. My router shows 270 when no clients are connected to it and throughput is actually zero.
If it is now different than in previous builds, it is likely due to the number being reported more accurately.
So...if that number is dropping from 270 something is interfering with the signal.... _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
I understand that even though it says 270 it may or may not be running at that. The problem is now its "Stuck" at 54 (Real Speed) which taking overhead into consideration is not fast enough to stream the crap i do from one side to the other. Trust me I understand theory...except this isnt a "Theory" problem.....This is a real Problem
Obviously if the connection quality or devices drop the max connection speed down to 54, your throughput will not be more than this. Having a G client will do that, but that shouldn't be possible with a NA only connection. To get higher speeds you would need to fix your status first. My point was that you need a good signal quality to do that.
There was a issue I was having with a build where I could connect with a G device to an N only radio, but I think that was prior to the build you were using. You might try BS 12874.
Also, Freddie802 had some information on this, I believe. Might want to search some of his posts. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
I also just tried newd vs newd-2, hardreset in between...didnt make a difference...this used to work fine.
Be aware that 270Mbit/s is the theoretical throughput under perfect to near perfect conditions. Don't expect the best. I don't get any better than an average of 100Mbps, and I'm about 3 feet from the router.
Just wanted to mention, though you already know this, but being that close to the router you should definitely lower your TX to 28mw on the 5Ghz band.
zikronix wrote:
Im using the 5ghz radio to supply the back bone from the router to the bridge. and the g radio off the ap for wireless clients
I'm a little confused here. What is your primary router(AP) and how far away are your routers from each other?
_________________ R7000 Kong vpn 23550-R01 (Main Router)
WRT610Nv2 converted E3000 vpnKong 21661 (RB)
WRT600N v1.1 BS std-nokaid 13637(5Ghz CB)(2.4Ghz AP)
WRT54G v5 BS micro 14684(RB)
Just wanted to mention, though you already know this, but being that close to the router you should definitely lower your TX to 28mw on the 5Ghz band.
[/quote]
zikronix wrote:
Im using the 5ghz radio to supply the back bone from the router to the bridge. and the g radio off the ap for wireless clients
I'm a little confused here. What is your primary router(AP) and how far away are your routers from each other?
[/quote]
My TX is set at 30mw (when I was testing they were only 3ft from each other, this was to try to figure out wtf is going on) on average the routers are 50 ft apart in a tile house. I mentioned that it used to report 270 with an actual speed of about 160-200Mb
now for what ever reason it sticks at 54 which taking in to account for over head of the bridge id piss poor.
Heres the config
Router #1 (main ap)
2.4Ghz for wireless clients (Has been set to mixed or g only)
5Ghz for backbone to bridge
Router #2 (bridge)
2.4G Off
5G, configured in client bridge mode
All devices on the bridge recieve their ip, etc from the main ap
The thought that, If you have G device connecting to the network it will lower speeds...thats not the issue here for two reasons. 1) Im using two totally different radios, not a single wireless client is connecting to the 5G radio. 2) thats against "N" standards. N is supposed to operate at full speed at all times no matter the client technology connected.
Remember everything worked fine until i flashed it with a new eko firmware. Rolling back did not fix the problem. It appears thed radio is operating at A speeds and not N speeds.
Remember everything worked fine until i flashed it with a new eko firmware. Rolling back did not fix the problem.
That would imply the problem is somewhere other than simply the build number, wouldn't it? How could the older build "know" you had a newer one previously flashed?
Remember everything worked fine until i flashed it with a new eko firmware. Rolling back did not fix the problem.
That would imply the problem is somewhere other than simply the build number, wouldn't it? How could the older build "know" you had a newer one previously flashed?
well i know its not the N radio on the 5ghz being a problem. Because the fluke tools can connect to it fine...and im not the only one having this problem so its gotta be config or bug...and the old firmware wouldnt know unless the 30/30/30 isnt wiping something from the nvram or there is something left behind even after reflashing...tonight im going to the linksys firmware and then ill flash back. see what happens.
