NPO Compositor adapted NRTOS 9.0.2

Tag : MIB

Dec, 2020

NPO Compositor adapted NRTOS 9.0.2

It took more than two years to adapt the Compositor 9 software from Compositor Software into Russian language. NPO Compositor has done a great job of introducing new functions and protocols into Compositor 9. The interface and documentation has been translated into Russian language and consists of chapters on IP switching and routing (2700 pages in total). It allows classifying this software as network real-time operating system (NRTOS). Compositor NRTOS 9.0.2 package consists of the real-time operating system itself with a graphical user interface executed on MaxMSP, Niagara software modem, which is a sample of a real-time moment (into which this sample was recorded) made with MaxMSP also, and an Android application RAD96, which inherited its name from the Compositor 9.0.1 main module (in 9.0.2 a22 assembly an extended version of this code is called VSF – virtual switching framework). All three versions have the same documentation as they access the same functionality. The difference is that RAD96 is an autonomous system and contains many more extensions that have not yet been issued. Compositor NRTOS 9.0.2 comes with 9134 extensions of management information bases, which were issued from the autonomous system RAD96 during the production of documentation. Niagara 32 software modem also contains a dump of this database (9134 routing tables). We also succeeded in classifying such an interface: by the type of execution, it can be considered a switching router, in contrast to the Compositor 7, which is considered a switch.

You can see the Russian language interface of Compositor 9.0.2 build a22 below:

Compositor NRTOS 9.0.2

Compositor NRTOS 9.0.2 channel matrix

The command language in documentation can be used within amateur radio terminal software such as TrueTTY on Windows and DroidRTTY on Android. This means that you cannot program the NRTOS directly (only via MaxMSP graphic user interface) but you can issue this commands through a teletype operator working in your autonomous system. Such an operator usually is a part of telegraph services still acting to the present moment. It is the only possible way to reprogram an autonomous system.

Seven protocols, implemented by NPO Compositor for version 9.0.2, enable communication in the Ethernet network. At the testing stage Compositor 9.0.1 was used mainly for packet protocols of amateur radio, but now in version 9.0.2 communication is carried out in the Ethernet network using the protocols used for switching and routing in this network. NRTOS includes 6 interior gateway protocols such as RIPv1, RIPv2, OSPF, OSPFv3, RIPng, EIGRP and one exterior gateway protocol for communication between autonomous systems (BGP – uses IPv4 version of the protocol). In addition, external communication is possible through 6-to-4 GRE tunneling.

Compositor 9.0.2 implements stateful and stateless NAT64, it can be used to create L2VPN and L3VPN services by exporting firmware in WAV and AIFF formats. Conversion from IPv4 to IPv6 is done on the fly in the NRTOS and makes it possible to map a single IPv4 address to multiple IPv6 destinations. As you can see from the Compositor 9.0.2 interface, it is a BSR router and is responsible for loading the system. Such a system consists of extensions that allow the server to participate in various workgroups. Compositor 9.0.2 is the installation program for the CP-6137-960FX server, to which this site is dedicated. This server is the only machine capable of generating emissions from the autonomous system RAD96 and this is its main value.

9134, Android, BGP, Compositor 9.0.2, CP-6137-960FX, documentation, DroidRTTY, EIGRP, GUI, IPv4, IPv6, MaxMSP, MIB, NAT64, Niagara, NPO Compositor, NRTOS, NRTOS 9.0.2, OSPF, OSPFv3, RAD96, RIPng, RIPv1, RIPv2, Russian language, switch, switching router, translation, TrueTTY, Windows

Apr, 2020

By ruslany

RTOS version 9.0.2 a16 assembled

It took more than 1.5 years to work on solving the problem of Compositor AV Extended interface break-through (which is the main interface of RTOS). This problem occurred during the dial-up of routing tables for establishing a tunnel connection. The way to recreate it: first, RTOS protocols are dialed by injecting routing tables into them, and then RTOS interface is turned off and on again. When the interface turns on, the entire database of the routing tables, which fills the buffer, floods into the interface, which cause a man in the middle attack, that is, an attacker gained access to the interface and induced it to inherit the route of its device. During this time, I made emissions in an attempt to understand how to solve this problem and, finally, it is solved. Now it is possible to configure each protocol from the passive interface state and take a pause while turning interface off in order to listen to the remote channel, and then go into passive mode again. Thus, you can achieve resolution from each of the seven RTOS protocols.

In Compositor RTOS 9.0.2 a16 it is possible to set one interface identifier for the entire protocol configuration session, and to do the training only in passive mode, as previously assumed. The next task in debugging RTOS is the fight against constants. It is one of the most important tasks of both radio security and cybersecurity. Through the introduction of constants, Ethernet devices position themselves, occupying the most convenient places in the network topology. This mainly applies to devices that frequently change IP addresses, such as smartphones and laptops. In order for the RTOS core to take priority of the host, the device must serve as a host for many devices. This is confirmed by Compositor Software database, which has been expanded to 8156 management information bases (MIB). Now that the Compositor RTOS manages a database of more than 8,000 devices, CP-6137-960FX server can be considered as a host, regardless of its physical connection to the network, through the Internet service provider. In fact, what I’m doing now is the continuation of the development to include more VLAN’s and create a VPN network segment. In the latest build, I have already managed to “shoot” the packets in several sessions. You can hear one of them below:

This method of feeding wave tables is a priority for communication devices, because it helps to break the synthetic ether by packet transmission. Since there are many packets, and each of them carries different information at different moments of time, the semantic base of the Compositor RTOS language is explained. In view of this, it makes no sense to enter the names of packets in the main interface, and I need to leave them in a VRF tables section only, focusing specifically on the tunnel windows. In addition, this approach allows using the Compositor RTOS interface as a tunnel interface with the ability to connect to multi-channel protocols, such as OSPF.

8156, Amateur Radio, Compositor, Compositor AV Extended 2.0, CP-6137-960FX, cybersecurity, interface, man in the middle, Management Information Base, MIB, OSPF, packet radio, packet translation, radio security, RTOS, Tunnel, VRF

Jul, 2019

By ruslany

Boosty – Forest People (FP mark emitted from the Ethernet)

Ruslan Yusipov Boosty and Exalted projects are valuable to the Russian Authors Society as they have previously unreleased and never heard routing paths. These projects have such routing paths, which are only heard of by the author. One such routing path is Boosty – Forest People produced in 2009 and never widely available to the public to the extent that only the author knows about its existence. Two unmastered versions of Forest People routing path loaned for emission. They are Dub version and Original mix. The routing path is produced in Boosty studio and remains unsigned and unlicensed to that day (unsigned at the present moment). In accordance with that I decided to make a fourth place emission of 281 routing tables. The emission named by FP mark has the most active navigation.

Using the dump of 5557 wavelets I made the job of translating 127 pages of English documentation on Russian language. This documentation is a continuation on CP-6137-960FX server development and is the modular switch of Compositor RTOS type installation manual. Using the injection of this dump I was able to do this job in a working week time. Injections were made by listening to a dump using insertion of Ultimate Ears ear monitors with dump playback of three times every four hours. The sum of injections was from 6 to 9 playbacks a day.

It was a robust experience and it forced me to do the job faster.
Ruslan Yusipov

You can taste the injection of this dump by listening to it by the link below:

RTOS dump at 192 kHz MIB 5557 15.07.2019 FWL

5557, Boosty, documentation, dump, emission, Forest People, FP, MIB, routing tables, RTOS, switch installation

Jul, 2019

By ruslany

Connection to RTOS from geographically remote location

Two-week experiment of connecting to RTOS from geographically remote location is finished. During this two-week experiment I connected to RTOS from the territory of the other country using the RTOS dump, which is recorded using wavelets only. Dump includes 5276 routing tables and communicates with the authorization point of 18 June 2019. This is 192 kHz dump and it authorizes RTOS in all available bands of radio spectrum.

RTOS dump at 192 kHz MIB 5276 18.06.2019 FWL

Zhoekvarskaya cavity

Tests performed during experiment:

Satellite TV channel matrix injection;
Routes deployment to RTOS MIB routing tables using generic navigation;
Remote connection to RTOS of other producers.

As the device for connection of RTOS I used rewired mobile phone on Android 4.4.2. It is rewired using four 64-bit middleware files, which are the part of RTOS MIB and are master filters for Ethernet injections. This mobile phone is autonomous in relation to other devices of that operator (the name of the operator retain unknown due to ethical considerations). In other words, it does not allow producing injection of a single routing table or routing path from the 3d party manufacturers. In attempt of 3d party applications to perform the injection, the mobile phone just stops this application operation. As stated earlier, this mobile phone can work only with Compositor RTOS 9.0.1 MIB.

Experiment 1: Satellite TV channel matrix injection

Using RTOS dump and the virtual optical port knowledge (in that experiment I used the configuration with virtual electric port), I injected the channel matrix of Russian digital TV. Experiment was successful attaining the full signal strength on the territory of sovereign state. Small bufferization errors are possible, because the host mobile phone, used to inject dump, does not allow using authorizations higher than z16. For this experiment I mainly used the CA (Cavity) emission, of the Cavity routing path. I used the orientation of virtual electric port in relation to signal constellation of satellite group, oriented on a Polar star. This experiment evidently shows, that for injecting of a channel matrix of satellite TV there is no need in dish type antenna, only the virtual electric port is needed and RTOS dump, loaded into a cell-phone. Experiment is conducted from a state of silent channel with no signal at all to injecting the channel matrix by dump with signal appearance, by the right orientation of virtual optical port on the Polar star.

Experiment 2: Routes deployment to RTOS MIB routing tables using generic navigation

In conductance with the first experiment the full navigation by all routing tables included in RTOS dump was attained. The geographic position was selected to achieve a bad signal reception. The object was situated in a cavity with mountains height of 500 to 800 meters. In such cavity the signal propagation is strictly limited, and so the technology of virtual optical port proved to be good.

Experiment 3: Remote connection to RTOS of other producers

In a trip, there was also checked the compatibility of 3d party manufacturers RTOS systems. In particular, virtual optical port was tested against Eutelsat 36B software, which performs the broadcasting on this region. The substitution of the channel matrix performed on the virtual electric port input, which performed a signal reception from mobile phone. The phone, on its own, performed the navigation by the routing tables, transferred through the dump. For this 9 to 12 dump injections during a day were made.

Android, Cavity, channel matrix, dump, emission, Experiment, MIB, RTOS, Satellite TV

Jun, 2019

By ruslany

More than 80% wavelets in MIB of RTOS

On the present day there are more than 80% wavetables processed to wavelets in the management information base of RTOS. Script allows processing up to 5 wavetables in a minute that is why full processing will take some time. To the end of this week the whole MIB should be processed on wavelets. This will allow creating two identical bases for two RTOS systems. The first base will contain wavetables only and will be used in the version of RTOS with the pass through of the second derivative of a function in the virtual console port. The second base will be wavelets only and will be used in version of RTOS with the second derivative of a function on auxiliary output.

The first version will support maximum up to 5-omega direct and aux regeneration speeds and is more like Ableton Live 10 engine. The second version doesn’t include the pass through of the second derivative of a function and has auxiliary speeds up to 150-omega. Such version allows authorizing all 7 levels of generic feeders simultaneously, which is more suitable for injections with authorization, because there is no need to fight for authorization on the predefined level, as all levels connected simultaneously. From the other side, the first version is interesting, because of the musical results, which it can produce, when I record middleware from routing tables. That is why I decided to maintain both bases and versions of RTOS simultaneously, which will grow with each emission.

Before a full transfer on the two bases was completed I recorded a final dump with mixed management information base, which includes the Boosty – Mini Bikes track emission. It is an interesting minimal techno composition with active use of hardware virtual synthesizers and analog sequences on bass parts. This emission includes 127 routing tables.

RTOS dump at 192 kHz MIB 5276 15.06.2019

5276, 80%MIB, Boosty, dump, MIB, Mini Bikes, routing tables, wavelets, Wavetables

Jun, 2019

By ruslany

Dump, middleware and more

An enormous work was conducted this weekend on MIB vector optimization. At the beginning the full base was defragmented by clearance of the dump below:

RTOS dump at 192 kHz MIB 5149 08.06.2019

In addition, the switch to 11 kHz was made and stochastic selections were performed in a special edition of RTOS with a direct output on auxiliary channel (through). Later these ethers were recorded as middleware with PCM WAV container of 24-bit 11 kHz. You can listen to them lower:

Middleware 1 11025hz MIB5149

Middleware 2 11025hz MIB5149

Middleware 3 11025hz MIB5149

Middleware 4 11025hz MIB5149

16 middleware files were recorded, here I show you only the four. Then these middleware was filed to the special version of L1-L4 L6-L7 vRouter RAD96, which uploaded it on 96 destinations of L1-L3 layers. This way, the middleware was fixated. This method is different from direct submission to RAD96 master routing table, because RAD96 ether aggregator can exclude the predefined set of ether combinations and I was needed to attain to precise channel matrix of 52 channels.

After the full contact base was uploaded by stochastic selections of MIB5149 and dump, I made RTOS authorization again but this time mangling the sample rate parameter up to 192 kHz. This way, I updated links to all aliases and authorized the whole MIB on 192 kHz.

192kHz, authorization, channel matrix, dump, MIB, middleware, RAD96, RTOS

Jun, 2019

By ruslany

MIB 5149 and growing

CP-6137-960FX server MIB extended with one more emission and is 5149 routing tables now. This time the 2009 experiments with Waldorf Blofeld synthesizer were seized from the Ethernet. The recording of Intro to Boosty project Live in Studio 69 club was filed to vSwitch MDL12. The emissions were 142 wavetables, among which original ethers of routing paths, translations, and preparation material for further emissions.

You can listen to the dump of Compositor RTOS with MIB 5149 recorded on 08.06.2019 in audio file beneath:

Compositor RTOS dump 8×32 MIB5149 08.06.2019

2009, 5149, Blofeld, CP-6137-960FX, dump, MIB, Studio 69, Waldorf

Jun, 2019

By ruslany

The dumps future workstations can only read

We are get used to 8-bit SysEx dumps, many of us even listened to their audio presentations. However, how the dump of modern embedded real-time operation system sounds? Let’s start with the fact that modern operation system is 64-bit, which gives almost 8 times more dynamic range, than 8-bit dump. Moreover, RTOS dumps are written with 192 kHz sample rate. In this post I will sum up two dumps, which were made with MIB 4795 and MIB 5007, which allows saying about their origin only one thing: these dumps are the music productions on their own.

In essence, we are dealing with routing tables, reproduced on the high regeneration speed. But, my task is to find the source of these routing tables, the hardware and software system, which can read these dumps and respond not only with sequence of events, but with sound generators tuning, sound synthesis parameters and effects. This station should include 64-bit operation system itself, working with 192 kHz sample rate, which is critical to CPU working frequency.

Such DAW should allow reading dumps with a large dynamic range and perform settings in accordance to the loaded network map. I would like to achieve panning and equalization in virtual environment without human intervention, in addition it should be performed not by a topology of some algorithm, but to exist inextricably with routing path filed in the current moment.

I remind you that 8 routing tables mixture is sufficient for a complete routing path. Taking in account 8×32 matrix for such routing tables, they are aired on 32 destinations. This tells us about high load of RTOS channel in a moment of dump creation. The high load on output channels creates tasks on input channels, because communication is a kernel-loop relationship and performed in a cycle with consistent calls and answers. To receive the answer the calling system should set in a que, because only 8 input streams available in RTOS. That is why there is a constant insufficiency in RTOS, it can’t be covered even with high console port regeneration speeds, and because to upload routing tables into the buffers the time is needed where high regeneration speed doesn’t play any role.

That is why the whole MIB should be loaded using autoload with aliases for the full base without forced thrust. I repeat, that forced thrust creates a big que and events processed only using generic feeder interrupters that is why you should constantly monitor filed system statuses. Because, there are no injections in filed systems on such high regeneration speeds as 192 kHz, then it is needed an additional time to receive an answer. If you need to receive an answer immediately, you should run RTOS on discretization frequencies lower, than 192 kHz, where the injections happen all the time, but the quality of the answer will be lower.

Compositor RTOS dump 8×32 MIB4795 26.05.2019

Compositor RTOS dump 8×32 MIB5007 03.06.2019

192kHz, 64-bit, DAW, dump, MIB, que, RTOS, SysEx

Tag : MIB

NPO Compositor adapted NRTOS 9.0.2