This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
networking:router:mikrotik_wireless [2012/12/24 11:03] gcooper |
networking:router:mikrotik_wireless [2016/09/01 10:38] (current) gcooper |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Mikrotik Wireless Configuration ====== | ====== Mikrotik Wireless Configuration ====== | ||
+ | |||
+ | See also **[[networking: | ||
+ | |||
+ | **Station Modes**: http:// | ||
===== Sample Optimized Configuration ===== | ===== Sample Optimized Configuration ===== | ||
+ | |||
+ | This guy suggested upgrading to V6 for better wireless throughput, then: | ||
+ | |||
+ | < | ||
+ | /interface wireless | ||
+ | set 0 band=2ghz-b/ | ||
+ | no disconnect-timeout=5s distance=indoors frequency-mode=regulatory-domain \ | ||
+ | ht-amsdu-limit=0 ht-amsdu-threshold=0 ht-rxchains=0, | ||
+ | l2mtu=2290 max-station-count=12 mode=ap-bridge preamble-mode=short \ | ||
+ | security-profile=WPA2 wireless-protocol=802.11 | ||
+ | </ | ||
+ | |||
+ | ===== Another Sample Configuration ===== | ||
+ | |||
+ | Comments: | ||
+ | |||
+ | For some reason following settings improve throughput: | ||
+ | |||
+ | < | ||
+ | enable-nstreme=yes enable-polling=yes | ||
+ | hw-protection-mode=cts-to-self hw-protection-threshold=2347 hw-retries=4 | ||
+ | </ | ||
+ | |||
+ | I don't know why nStream should be enabled, but it was performed better with it than without it. And most important was: | ||
+ | |||
+ | < | ||
+ | ht-amsdu-limit=256 ht-amsdu-threshold=256 | ||
+ | </ | ||
+ | |||
+ | Decreacing AMSDU from 8192 increases throughput! I read opposite of this on many posts, but try it and you will see. | ||
+ | |||
< | < |