I tried to chang wireless default to only-hardware-queue on wireless interface with wireless-fp package on nv2 link…but throughoutput was less stable and dropped from 65mbit/s to 45mbit/s…
what is best to use for wireless if I want to use fastpath?
fast path is used when you use 802.11 an nv2 wireless protocol with wireless-fp package.
You haven’t provided enough information, please tell us more detailed about this wireless link (hardware,configuration, distance, tdma-period-size)
Try to reset the wireless cards configuration and test again.
How are you measuring the speed?
I cant reset configuration it is in production enviroment.
It is 802.11N, MIMO antennas on both side, on one side rb433ah + r52nM, on other side is sextant, distance is 500m, on both sides about 15 networks. Protocol nv2, v6.15, wireless-fp, tdma auto…
I test it using bandwitch test utility in ros…
what more do you need?
2 weeks down the road and still no answer? pfff. not very informative this way… maybe this post reminds uldis…
(Or did you figure it already out yourself?)
problem still persists…I cant reset wireless link it is in production enviroment…
try to set the tdma-period-size to 2 and check if the speed got stable.
Also please upgrade the RouterOS to v6.18
Can you explain why tdma-period-size should be 2? Not so much the number but the explanation why interests my.
I have 95% of my network (+30 routers in either backhaul or AP (wireless) mode) and they all work fine it seems with fastpath and hardware queue on the interfaces.
I only have one rb800 which has one AP radio with 37 clients in a mixed range from 2km up to 8km and here the wireless fp package completely destroys the AP-network.
Since NV2 with its tdma period size and the hardware queue and the fastpath setting all seem to have a relation with each other I am trying to get more in-depth information on why I run into problems with rb800
[And maybe the problem in the rb800 only surfaces because it has by far the most clients connected to one AP radio, that are also have a relative high distance range for these clients that also all are working in single chain mode protocol N with 20Mhz channel width.
I played with several settings, like the tdma-period-size, the channel width (but run into interferences with other AP), fixed or default conn. rates+MCS rates but the only thing to bring the network back to normal again is disabling wireless-fp package to use the normal one again. I made a ticket for this issue but so far no answer… (couple of days now..)