I assume your doing routing with your setup since you say your not doing any bridging.
Would help to figure out what coudl be causing the problem knowing more about your ip setup. Also when your running the test check the CPU load on the AP unit.
Generally bridging IMO will not help you except maybe resolve some IP issues that could be easy to fall into trap. Either you have to use WDS and bridge or create EOIP between the two CPE units.
Means that you have the TX/RX rate set on the wireless interfaces to these rates, then you should change that to allow lower rates – perhaps you lose a packet then a client/station has to reregister – which takes some time and slows the link down more.
To Tully I can say, that the tx/rx is the negotiated speed. I have found, that reducing the tx-power to 17 - 18 dBm gives a better connection. Now I get clean 10 Mbps over the two hops.
The ip setup is:
station 1, wlan: 10.72.1.200
station 1, lan: 10.76.1.10
AP, wlan: 10.72.1.100
AP, lan: 10.74.1.10
station 2, wlan: 10.72.1.1
station 2, lan: 10.67.2.10
The setup is based on static routes - and normally this kind of job is not a problem for me Furthermore, all routing works as it is supposed to.
At the max. throughput, the AP cpu load is at 85 - 90 %, which means that we are close but not quite there…
I test both situations between two directly attached mikrotik routers with the included bandwidth testing tools. This means, that the bandwidtht testing software runs on different cpu´s (2.8 GHz P4) than the routerboard based radios. The reason for this is, that the testing tools are consuming a very high amount of cpu-power.
I use UDP testing one-way. The numeric results with udp-testing are generally higher than a real ftp-transfer between the two routers.