I think is not a MikroTik problem. With these bandwidths, latency plays against.
I think one main problem of NV2 is the jitter of the latency. TCP frames arrive asynchronly to the NV2 TDMA time slot, sometimes they get through within 1ms mostly within 3ms, but sometimes with 15ms (one out of 100). Maybe - just a idea - it would help to delay the incoming TCP frames of a PtP link by a certain time - so that over the link - the ping time is always 15ms. This would be a big benefit for the TCP timing algorithms in the client computers.
The idea as example: (ROUTER A and B have a synchronised time base t
, I write this time count in front of each of the following lines)
(37) - ROUTER A get packet from ethernet interface and measure the packet timestamp: ta=t
(37) - some delay...
(38)- ROUTER A send this packet
( )- wireless link with max delay tmax (e.g. 15)
(42)- ROUTER B get packet and timing information ta
(42)- ROUTER B queue the paket for the time ta+tmax = 52
(42)-ROUTER B queue waits until timestamp reaches t
(52)-ROUTER B will send packet out over the ethernet interface
Can this "ping equalizing" be done with current mikrotiks? Can I mark and timestamp packets and send this packet-marks to another router?
Can this be done with linux (e.g. rasyberrys)? Maybe it is sufficient to synchronise both clocks over the links (statistically over a longer time) or use GPS modules with PPS output...