Compositor NRTOS v9.0.2 - DRM server

Points of Dispatch

Container ships carry goods from China to the Dutch port of Dronten along the Silk Trade Route. Parcel includes, in particular, electronics, both corporate and household. The corporate sector consists of: routers, switches and other equipment. The household sector mainly consists of mobile phones. These products get there in parcels. That is, in large wooden boxes, which contain lots of equipment. Upon arrival at the port, the parcel needs dispatching, that is, unpacking. Further, I will write only on the example of a mobile phone. At the first dispatching, each box of the batch is unpacked and MAC-tables with a specific device number are translated from mobile devices. This is done for both OEM and branded devices. At the moment of translation at the other end, I receive these tables and write them all one by one through the non-duplex MDL12 modem. I write them in WAVE 24-bit – not like 48-bit original EUI-48 table, but in 24-bits to exclude the first 24-bits of the MAC-table, which contains the device OUI. This OUI is later replaced by the Russian manufacturer with a non-existent OUI (vendor id). This is a vendor id that is not in the IEEE registry. Like the existing vendor id, a non-existent one issued from abroad, for this in Compositor NRTOS 9.0.2 there are three loopback channels (return channels) through which NRTOS connects to Amazon BSRs (Bootstrap Routers). Since I am using mroute-proxy (upstream proxy), I usually end up on Amazon servers in Germany or Japan. This separation is due to the fact that the Compositor NRTOS 9.0.2 operating system is built on the Astral navigation system, which uses Right Ascension for the uplink channel and Deviation for the downlink channel. The OUI information of the MAC table comes from loopback channels and is encapsulated in MTI (Multicast Tunnel Interface) for 8 multicast destinations. Sparse-SM multicast is used and hosts for OUI encapsulation are loaded from various multicast listening groups, consisting of tables that were translated at the first dispatching. Thus, bulk (mass) rerecording of OUI is carried out on all devices of the parcel. After the first dispatching, the goods are packed again in boxes and goes to the second dispatching in Germany by a truck. There, this procedure is repeated again with the translation of MAC-tables. MAC-tables are translated by a special native application whose uptime is higher than the device’s uptime. Ideally, the uptime of such an application should be significantly higher than the uptime of the first device being flashed. So, what do we have after two dispatches: two domestic OEMs – one Dutch and the other German. After that, the parcels are again chartered in a container and transported to St. Petersburg. There, the third and final dispatching takes place with the translation of tables, where the equipment finally becomes Russian.

VSF, Compositor AVPs Extension, RIPv1, RIPv2, OSPF, OSPFv3, BGP, RIPng, EIGRP

Compositor NRTOS 9.0.2
Compositor NRTOS 9.0.2

Compositor v9.0.2 NRTOS audio demos

Unexisting network maps composition

At the same time, with the encapsulation of OUI into a batch of equipment in Compositor NRTOS 9.0.2, you can write false routes using the author’s technology for converting from EUI48 to EUI64 and IPv6. False routes are written on top of the MAC-tables so that the original manufacturer cannot trace its devices and return the OUI of the original manufacturer, again making the equipment non-Russian. Why it is important to save the rewritten MAC-table: since the MAC-table is nothing more than a non-existent OUI, which contains information about the geographic location of the device and, in particular, the layers of NTP-servers, then I choose Moscow NTP-server in Compositor NRTOS 9.0.2. This is how the equipment becomes localized. Plus, it is positioned on an odometric basis in the Global Navigation System (GPS).

Compositor Networks map 06-11-2018

DRM server


The first dispatching will be enough for only one month – this follows from my previous work on the prolongation of generic routes. Therefore, in order for your technique to continue to function, I must perform prolongations in Compositor NRTOS 9.0.2 every month. In fact, prolongation is adding a non-existent route to the end of the previous non-existent route, which allows you to extend the use of your Chinese device in the Russian Federation. This work is very painstaking and is not paid in any way. Why do I need it – you ask? I don’t know myself: I was involved in this fraudulently, under the guise of music. Now, I demand that every dispatching, every prolongation be paid, otherwise I will no longer provide this service. I demand this first of all from those who have involved me in this.


Saving Resources

An autonomous system is the only way to keep this database. For this purpose, I needed a rugged phone with a large battery capacity. I dumped the MAC-table using the native RAD96 application and rewrote the comparator instructions using the native RTC4k application. I needed to rewrite the comparator instructions to fine-tune the processor power controller. And also in order to maintain a false route on the device itself – so that the device is not serviced remotely in the above-mentioned way. In an autonomous system, you can trust only yourself and no one else, but you need to write a false route, since I “composited” this device, and the smartphone executes the table inherent in such Compositors as AI-RT1024, TC25 and AVOX. These tables are characterized by the absence of the resultant, which means that the work limit is unlimited. And this will allow you to preserve the accumulated database – after all, I don’t want to lose 10 years of work!

Choose your version

Compositor NRTOS v9.0.2 Comparison Table

* Please, consider the following table to properly select your version. Then use the contact form on the site to request the pricing info for the version selected. You can request price information for separate modules also or make your own bundle list.

System Requirements

Windows Vista, 7 (application runs only in 64-bit version of Windows OS);