For this to work, there are two solutions :
- the radio clock need to have an input for a sync reference, and a sync generator is needed to generate the sync carrier on the right frequency.
- the radio clock need a VCO clock, voltage controlled oscillator, so that it is possible to adjust the transmit frequency very precisely.

I think you have the wrong idea about the sync. My impression is that protocols like NV2 are TDMA. The purpose of syncing the transmitters on a tower would be to coordinate that they are transmitting and listening in unison to ensure weak signals from a client aren't drowned out by an adjacent AP. The Time of Day clocks in each AP probably run at microsecond or better accuracy so all you are trying to do is make sure that the transmit interrupt (or DMA transfer to a radio's own tx buffer) all happens in the same instant. It isn't to try and make sure their transmit centre frequency is locked precisely to 2.412GHz for instance.

will we be seeing MSTP in 6.40 (a latter RC) perhaps? is it in planning?

Has it been promised?
In case it has, can you provide a link, please?
If not, please stop spamming with the topic not directly related to the 6.40rc series.

v6.40 will have another separate VLAN-aware bridge implementation

We could think how to sync the APs that are on different frequencies but located on the same tower and connected to the same ethernet network.

You could take some ideas from or use PTP (https://en.wikipedia.org/wiki/Precision_Time_Protocol) to synchronise the APs internal clocks over ethernet and hence transmission times from a collection of APs on a tower without having to mess with GPS. You only need relative not absolute time synchronisation. How well it works depends on how quickly you can get an incoming ethernet frame timestamped - but the articles all suggest sub-microsecond is possible.

Please do some minimal work on the IPv6 routing..

Please do some minimal work on the IPv6 routing..

+1

Version 6.40rc20 has been released.
*) wireless - fixed rare crash on cap disable;
.

*) fasttrack - fixed fasttrack over interfaces with dynamic MAC address;

IF mikrotik guys are working with dhcp part of ROS, its time to answer - when mikrotik will implement dhcp option 82?
Actually is interested lease issue by circuit-id.
Mikrotik stuff, c'mon you did half of work, go on and finish.

IF mikrotik guys are working with dhcp part of ROS, its time to answer - when mikrotik will implement dhcp option 82?
Actually is interested lease issue by circuit-id.

IF mikrotik guys are working with dhcp part of ROS, its time to answer - when mikrotik will implement dhcp option 82?
Actually is interested lease issue by circuit-id.

we've been using this since 2008 you just need external RADIUS

:global test "test"

:put $test

Scripting language has two types of variables:

global - accessible from all scripts created by current user, defined by global keyword;
local - accessible only within the current scope, defined by local keyword.

script 2 must be:
:global test;
:put $test

sindudas - You should be able to add up to 30 interfaces. Are you sure that simply menu did not go out of your computer display?

sindudas - You should be able to add up to 30 interfaces. Are you sure that simply menu did not go out of your computer display?

Forbidden

You don't have permission to access /link/mikrotik-vlan-add.jpeg on this server.

Forbidden

You don't have permission to access /link/mikrotik-vlan-add.jpeg on this server.