Mikrotik How To

Mikrotik 802.11a/b/g/n High Power MiniPCI card - 350mw output Atheros AR9220 chipset
High power (~350mW with RouterOS) miniPCI wireless card for special applications.

R52n is a wireless 802.11a+b+g+n miniPCI card for multiband high speed applications, with up to 350mW output power. It works on 2.192-2.539 and 4.920-6.100GHz frequency range and supports Turbo mode for faster transfers. The card performs best when coupled with the MikroTik RouterOS. R52n is optimized to work with MikroTik Nstreme protocol to reach extra long distances at a great speed. The Nstreme protocol is MikroTik proprietary wireless protocol created to overcome speed and distance limitations of IEEE 802.11 standards and to extend point-to-point and point-to-multi point wireless link performance.

Specifications
Chipset : Atheros AR9220
Standards : IEEE802.11a, b, g,n
Media Access : CSMA/CA with ACK architecture 32-bit MAC
Security : Hardware based 64/128 bit WEP, TKIP, and AES-CCM encryption WPA, WPA2, 802.1x


NOTE: This 802.11n card requires RouterOS version 4.03beta or newer and a key update before it will be found in your RouterBoard miniPCI card slot. Instructions are on the Mikrotik wiki in the 802.11n Setup_Guide.

This card will not be recognized in older RouterOS versions. The key update is free but does require an Internet connection.

SKU R52n
Weight 0.03 lbs

I Try this configuration at mikrotik 4.x os version.

/ip firewall mangle
add action=mark-connection chain=input comment="" disabled=no in-interface=ether2 new-connection-mark=int_conn1 passthrough=yes
add action=mark-connection chain=input comment="" disabled=no in-interface=ether3 new-connection-mark=int_conn2 passthrough=yes
add action=mark-routing chain=output comment="" connection-mark=2 disabled=no new-routing-mark=route1 passthrough=no
add action=mark-routing chain=output comment="" connection-mark=3 disabled=no new-routing-mark=route2 passthrough=no
add action=mark-connection chain=prerouting comment="" disabled=no dst-address-type=!local in-interface=Lokal new-connection-mark=pre_conn1 passthrough=yes \
per-connection-classifier=both-addresses-and-ports:2/0
add action=mark-connection chain=prerouting comment="" disabled=no dst-address-type=!local in-interface=Lokal new-connection-mark=pre_conn2 passthrough=yes \
per-connection-classifier=both-addresses-and-ports:2/1
add action=mark-routing chain=prerouting comment="" connection-mark=pre_conn1 disabled=no in-interface=Lokal new-routing-mark=route1 passthrough=no
add action=mark-routing chain=prerouting comment="" connection-mark=pre_conn2 disabled=no in-interface=Lokal new-routing-mark=route2 passthrough=no

Prerequisites:

Make sure that the WRAP board has the latest BIOS.

Notes: The WRAP board and Router OS take different com port settings in HyperTerminal. If you want to see the actual boot text from the WRAP board, not router OS, you have to change your setting to:

Configure your terminal emulator for 38400 8N1 (default baud rate), no handshake. To enter
setup, type S during the memory test. You should see somethink like the following:
PC Engines WRAP platform

tinyBIOS V1.4a (C)1997-2003 PC Engines
640 KB Base Memory
64512 KB Extended Memory
01F0 Master 848A HYPERSTONE FLASH DISK
Phys C/H/S 497/4/32 Log C/H/S 31/32/63
WRAP setup
(9) 9600 baud *3* 38400 baud
(C) CHS mode *L* LBA mode
(X) Xmodem upload (Q) Quit

What you can expect to see from time to time is something that looks like misc characters on HyperTerminal. When you have it set to the RouterOS settings, the misc garbage is the WRAP board information. When you have HyperTerminal configure for the WRAP board com port settings, the misc garbage is the RouterOS software.

The default setting for the RouterOS software is: 9600 8-N-1, with no flow control.

Note: Be absolutely positive that you are installing to the correct removable media.

This screen actually takes quite a bit to do anything, so be patient. After a while you will see the following:


Once it gets to this point, it will reboot. Again, the time for this process can vary, so give it some time. It may actually hang at this point, though. If it does, pull the power and let it recycle. Even with a reboot, though, it may actually take a little longer to boot then you think it would. After it boots, you will see the following:


At this point, you can either work from the command line, or swap to Winbox. If you choose Winbox, just use the appropriate Ethernet cable and plug into your computer, or plug your RouterOS box into the same switch your computer is using. You don't even have to know the IP address, since Winbox will pull up the AP by MAC address:
(q4)

You should understand that for 802.11 devices there is really limited amount of information (or "feedback" from the environment) that devices can use to tune their behavior:

• signal strength, which could be used to figure out best transmit rate knowing receiver sensitivity. Sill this is not reliable taking into account that sensitivity for different receivers varies (e.g. changes over time), path conditions are not symmetric (and device can only measure signal strength it receives), etc.
• by receiving/not receiving acknowledgment for frame sent.