i know that they showed a demo of 802.11n at the mum in the us and now that the 333’s are available does any one know where i can get a couple of n cards for the 333?
this is not limited to RB333, but to Software. We have not yet released a N package. There will be an announcement when we do.
for max throughout you will need a fast cpu anyways.
remeber: an atheros ar5008 and 2nd generation AR90xx 802.11n chipsets will be delivered with Two and with Tree Radios inside.
for full throughpout with a AR5008-3NX chipset card with 3x radios you need some cpu power - at the moment seems the limit about 100-110 mbps raw throughput … but RB333 is too slow for this probably …
The quite high power consumption of such cards is another issue , the very first ar5008-3nx ABG-N cards i have here on my desk use up to 6 watts under heavy load and they have also quite high thermal emmissions…
i hope the 2nd generation 802.11n chipsets with Atheros AR90xx chipset have lower power consuption, mass production of these cards start very soon …
RB333 CPU will handle 802.11n.
We will release the drivers for 802.11n together with the full release of the RouterOS v3.0
So if the RB333 router board can handle 802.11n, why am I hearing people saying they can’t wait until MikroTik will announce their support for the 9000 generation of Atheros product so they won’t be stuck with just the option of LSX and alternate solutions? I hear people talking about this and I just want to understand why?
If you install other OS than RouterOS on your RouterBoard, you can run 802.11n if there is drivers!
But then all the good stuff is gone ![]()
But we need all the good stuff, that’s what makes MikroTik boards, MikroTik boards. Does anyone or has anyone heard when they will be releasing a new board that is 802.11n compatible and has all the good stuff?
The term “compatible board with 802.11n” does not exist. Every board can work with 802.11n cards.
The problem is in OS and drivers/support.
I think Mikrotik won’t release N support for at least 6 months becouse the drivers for linux are still experimental and the AP mode don’t even works (there’s some proposed patches for this). There is also alot of reports on kernel freeze and other weirdness.
So far, the N cards only work fine in legacy (a/b/g) modes.
N is an option in the band settings now. Not sure what that means exactly.

Exciting !
Means probalby there’s some error becouse AR5213 does not support N, and MT does not even support N cards in legacy modes (abg/bg).
With the amount of hints that have been being dropped recently, N support would not suprise me.
I highly doubt that.
802.11N (not legacy abg modes) cards are simply not ready and not working in madwifi drivers, which means in linux also.
And MT is, as we all know, based on linux.
I still never saw even one successfull story with 802.11N ap+client based on pci/pcie cards.
not true. we don’t use madwifi or any other linux driver for wireless.
802.11n is already in testing for a long time, so it will be ready soon
P.S.: all laptops now come with N cards, and there are tons of N APs too. They work great.
anyone work AR5008-3NG(Atheros AR5008-3NG AR5416+AR2133) (WMIA-207GN/EU) with mikrotik ? or Kamikaze ?
or is there any madwifi drivers for it ?
Best Regards;
Thanks.
If the driver will be added to MT soon - that’s great.
There, however aren’t any 802.11N AP based on PC with PCI/PCIe card on linux. Embeded platforms like wrt610n doesn’t count.
Can you, by the way, explain how the guy above got N mode for non-N card? bug?
“madwifi” driver is soon going to be obsolete and replaced by ath5k driver, and for your card (AR5008) you would look for the ath9k which is still in experimental stage and very buggy. You may also have alot of trouble to make it work.
Openwrt (Kamikaze) have, at the first look, working solution but as they are based on ath9k they:
- do not have N mode in both AP and Client but only legacy (abg)
- do not have AP mode working (or i couldn’t be able to set it up)
- not all “distribution” of kamikaze support the above - look for the one that have ath9k drivers package
There, however aren’t any 802.11N AP based on PC with PCI/PCIe card on linux.
that’s why you need MikroTik
![]()
- clients MikroTik, Windows, MacOS
- APs MikroTik
That’s true…
Not mentioning the fact that N AP/Clients in MT would probalby work much better and stable than other platforms.
I wish for 40Mhz channel and antennas switching (on-off) in first release. ![]()
Is there some list of what Cards/Chipset will be supported in MT? Some Atheros N cards are buggy.
Is there any further news on the 802.11n support?
We have an RFP, and I would really like to use Mikrotik as the SBC software.
Cannis
From the test of 802.11n AP and 802.11n client which consisted of combination of D-Link DWA-547 PCI wireless card and Linksys WRT160N device i have next results:
- PCI card (client) connected to AP (Linksys,DD-WRT) have greater troughput than Linksys-Linksys, and it’s about 67 mbit in perfect condition where the signal was -50 (62mbit with Linksys-Linksys).
- Official Linksys firmware works faster than DD-WRT, with DD-WRT i got 67mbit and 74mbit with official and it’s not CPU bottleneck.
- N mode works very bad in rural areas that are full of noise, with 1km link i got 8mbit/sec in best case, and 1.5mbit in worst case. The signal was -60.
Since we got very bad result in rural area on 2.4GHz we should move to 5GHz to get good troughput.