Niagara modem is disabled on the NPO Compositor server

Tag : CP-6137-960FX

Apr, 2021

Niagara modem is disabled on the NPO Compositor server

On 9.03.2021 the work of the Niagara a15 i6 software satellite modem on the CP-6137-960FX server was terminated. This action was performed due to the disagreement of the author (Ruslan Yusipov) to timely issue from the RAD96 autonomous system. According to the author, the company that uses these emissions, namely the investor, owes a large penalty in the amount of 40234513 rubles. It refuses to pay it off with virtual and real funds. At the moment, the server works in unicast mode, using only the internal services of Compositor Software. The American office of the Compositor Software company asks to use only direct-services and not to include any sample-based modems with sample pay. Consequently, the statement of the NPO Compositor about zero-level aggregation is considered incorrect. Indeed, a moment in time is played, but the dump has a price, and each iteration of the dump playback is multiplied by the billing of the cost of the dump itself. Thus, starting the modem does not guarantee that the billing meter has not worked. In reality, this modem could only be started with a counter of the number of times the dump and real-time frame were played. Thus, the real aggregation has already significantly exceeded the allowed volume of the 4-node mainframe CP-6137-960FX. Regardless of whether the emission will be made or not, the volume of aggregated traffic has already exceeded the allowed 39204 iterations of the real-time frame. After releasing a new dump and a real-time frame, the counter will not reset, which indicates the accumulated emission. An emission can be made within a given number of iterations. That is, it is possible to issue an emission, but it does not make sense to write it to the dump, since in any case the aggregation counter has already passed the admissible values.

The Niagara project can be resumed only by setting the number of nodes to 256 (Intranet mode) on the RAD96 autonomous system, inheriting it from the Compositor Lite NTP server. Thus, the number of aggregation iterations can be increased to 2509056, which will allow the modem to be used for a certain additional time. You need to extinguish the mainframe of 4 nodes. Moreover, this is only one of the reasons for stopping the modem, another important reason is the following: to latch the time frame, you need to include more iterations in the minute dump, setting the network to 2 ^ 14 values, i.e. 16384 bpm. This is possible only on a different hardware platform, because the estimated playback speed of the CP-6137-960FX channel aux is 2 ^ 13 or 8192 bpm. The solution in this situation without purchasing new development platforms is to launch the Niagara software modem with the Compositor Lite NTP server. Otherwise, you will have to assemble a new stationary machine, buy a laptop to develop a new aux channel, and buy a new mobile platform for developing mobile applications also. This is considered impractical, since the development of all services and applications has already been completed – only the number of nodes, the speed of iteration of the channel aux and generics can change.

Another solution is to completely abandon platform tools such as Niagara, Compositor and RAD96 standalone applications based on the MaxMSP Runtime. Instead, it is proposed to use all the services accumulated over the years of project development at the kernel level of the Windows 7 operating system, i.e. Windows NT kernel. Since the services are assembled on an independent platform, they are not charged, but this requires the continuous operation of the CP-6137-960FX mainframe, which is currently impractical even with full documentation for a virtual optical port. Moreover, this documentation does not cover the most important issue that the CP-6137-960FX server provides a service mainly for devices from EUI-64, and these are devices that are not included in the Ethernet protocol. Thus, the recognition that devices from EUI-64 communicate with each other using a protocol other than Ethernet is the task of the IEEE 802 working group. Although initially it was believed that the Compositor software uses the Ethernet protocol, it is now becoming clear that this is not the case, because most of the devices from EUI-64 are not equipped with a connection using this protocol.

Compositor Software, CP-6137-960FX, EUI-64, IEEE802, Investor, Niagara, NPO Compositor, Penalty, RAD96, Services, Windows NT

Dec, 2020

By ruslany

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

Apr, 2020

By ruslany

Compositor Software builds virtual servers for Microsoft Windows and Android platforms

Compositor Software presents 4 architectures on C++. It is TC-TRSRRT2048, TC-SUBTRSRRT262144, TC-2SUBTRSRRT262144 architectures for STC2k, RTC4k, RAD96 and RAD36 platforms correspondingly. Now, when Compositor Software code repository have grown, it is time to move forward past the MaxMSP platform. First, Compositor Software thanks the JUCE framework for providing an ideal platform to make servers. Compositor Software would like to thank Iain Patterson for providing NSSM application, which helps creating daughter services and allows making full scale server out of company code, written on Gen~ platform. Of course, the main tool is and still the MaxMSP platform, because the original Compositor Pro 1 project was entirely made on MaxMSP objects and later rewritten using Gen~ object. It allowed exporting an authentic C++ code out of MaxMSP 6 platform. Additionally, we want to thank Cycling ’74 for providing a project to build exported code in JUCE and Microsoft for providing Visual Studio 2019 Community, which allowed to make final builds of Windows versions.

Before making standalone apps, Compositor architecture codes compiled from several minutes to 5 hours at runtime. Now, programs load in seconds and consume lower system resources than original MaxMSP Runtime applications.

Using Gen~ platform and JUCE it was possible to build RAD96 mobile application, which allows transforming your smartphone into a complete autonomous system with Compositor kernel of last generation. This way, Compositor Software moving into the IoT side conception to create a network of devices, controlled by CP-6137-960FX server, which runs the aforementioned services. This modification allows upgrading the device performance from Windows NT 4.0 kernel (Linux 2.6.18 kernel on Android) to 8^th generation Compositor kernel. It includes x2048 oversampling, digital shutter with interpolation, second derivative of a function and 8^th order Butterworth filters.

The desktop version of Compositor Software 4^th generation experimental kernel (TC-TRSRRT2048 architecture) has virtual accumulator module, which allows controlling the physical accumulator charge and performs charging each time network activity occurs. This kernel can be used on mobile platform also.

Compositor kernel architecture itself is a modular architecture if described by using physical blocks. The amount of modules depends on its usage. In base configuration, Compositor is NTP-server core service. In advanced configuration, it is L2TP client-server application with tunnel authentication capabilities. However, Compositor Software doesn’t set Compositor RTOS 9.0.2 as deprecated platform due to this move. It is only made because of the fact that pre-built application-service has much higher uptime in comparison to Runtime with dll modules of MaxMSP. The fact that, RAD96 mobile is on the constant expose due to the network presence on the device itself, CP-6137-960FX server supports its calculation, serving for distributed computation. It is performed using 2^nd order transfer function, which can stack a lot of devices with minimal expenditures, and RAD36 platform supports such computation by multithread 12-cores L1-L3 architecture.

Compositor Kernel, Compositor Software, CP-6137-960FX, Gen, JUCE, Linux 2.6.18 kernel, MaxMSP, NSSM, RAD36, RAD96, RTC4k, STC2k, TC-2SUBTRSRRT262144, TC-SUBTRSRRT262144, TC-TRSRRT2048, Visual Studio 2019, Windows NT 4.0 kernel

Dec, 2019

By ruslany

9.0.2 is officially Compositor RTOS

Now, after a great success of Hypervisor, I’m here to present to you the latest build of Compositor, which is a network RTOS in version 9.0.2 a11. I already revealed the protocols, which this RTOS is capable of, now, I just announce it’s existence to the public. As you can see on the image below, NTP-servers information is already implemented, as well as critical parameters such as Split Horizon with Poisoned Reverse revealed.

Compositor v9.0.2 RTOS (Mainframe)

Now, you may see this software as a virtual router it is not. It is mostly a full-scale modular operating system with connectable interface. By this I mean that you can route protocols to the interface and modify their processes. You can activate all protocols at once or just one protocol and select the protocol you configure in COMPOSITOR interface. VSF strictly names the process behind the technology implemented as you can stem and aggregate the protocols up to 32 processes each with VSF turned on. Compositor Software server CP-6137-960FX, however, already achieved aggregation of up to 960 nodes of VSF processes. This means that running NIAGARA client OS on CP-6137-960FX makes you available all 960 processes. For example, you can view Compositor RTOS as a software for CP-6137-960FX Mainframe, which is really a mid-tower case ATX server. This is all available thanks to the base of Royalty device boot loops, which I gathered through my producer career.

I continue working on the Russian documentation for CP-6137-960FX server in the face of updated software. Progressing by 15 pages a day sometimes less based on the workload. The return-on-investment to produce the translation needed up to 20 times a day. I simulate this process with e-roi dumps at speed, which is higher, making the whole process cost more and bringing more satisfaction to investor. Documentation greatly increases the cost of software compared to a MaxMSP student work (someone can estimate this work like this). I don’t feel pressure and rush to go beyond MaxMSP platform as it is not needed at the moment. However, Cycling already made steps to prevent me from doing export in the latest builds of their software, because they implemented MC, which is basically what I done first with RAD96 and later with VSF on Max 6 myself. Testing MC with generic processes showed me the fact, that using MC instead of VSF makes the whole process cost more to the CPU (8 MC processes can consume as much as 32 or even 128 VSF processes). So, MC not even close to the performance of Max 6 multiprocessor programming capabilities. I don’t even take in account that they cut down sample rate calculation by half since Max 7 to reduce cpu consumption. I managed to run Max patcher window not as a single-thread process, but as a multithread process even without the need to export and redesign software on purpose. So, it is a real redistribution example, when I run VSF processes of generic protocols on my mid-tower machine with 960 nodes turned on and performing like a real Mainframe server without need for cabinet case with lots of machines and tons of noise from cooling equipment. This makes available CP-6137-960FX in home environement with noise level less than 30dB and CPU temperatures not higher than 40 С even on highest workloads.

9.0.2, 960 nodes, Compositor, CP-6137-960FX, Mainframe, Max/MSP, MC, RTOS, VSF

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

5000 routing tables in CP-6137-960FX MIB

NPO Compositor reached the final goal of emission for CP-6137-960FX server, which is 5000 routing tables. Management information base is 5007 routing tables that allows organizing not only 4000 VLAN, but also 5000 VLAN. NPO Compositor will continue to expand the management information base up to 6000 VLAN, because each routing table gives access to its own VLAN trunk or autonomous system.

You can listen to that dump, which includes full 5000 MIB:

Compositor RTOS dump at 192 kHz with 5000 MIB on 03.06.2019

This dump allows you to authorize in Compositor real-time operation system and attain to its external control by RAD96 autonomous system. To connect to Compositor RTOS it is enough to playback that dump using streaming method in online player with RAD96 autonomous system turned on. In this case, autonomous system will serve as middleware, which will merge Compositor software and your equipment and will make remote connection to CP-6137-960FX server possible.

When NPO Compositor reached 5000 routing tables it gained the full MIB, which finishes L1-L4 L6-L7 vRouter RAD96 development. To order vRouter RAD96 licenses use Compositor Software contact form.

4000 VLAN, 5000 MIB, 5000 VLAN, Compositor RTOS, CP-6137-960FX, L1-L4, L6-L7, middleware, NPO Compositor, RAD96, VLAN, vRouter

Jun, 2019

By ruslany

Bessel beam for solving laser diffraction problem

You and I are probably familiar with a problem, which was set to the wide audience on protection from hypersonic weapons. Now, I can definitely say that a solution is ready – it is Bessel beam. Bessel beam, in a contrast with standard laser do not diffract and can be acoustic. That is why it can be used in any weather conditions. Returning to the post on laser stand, Compositor Software is ready to help us in this problem also. The thing is that beam physical modeling in Compositor RTOS is an exact 1^st order Bessel function and Bessel beam is formed in the virtual optical port. That is, it cannot be fixated for a long time using the standard tools.

And you should be assured there were a number of such tools. For example, MDL12 vSwitch spectral estimation in Ableton Live 9 showed that signal is formed in the bandwidth set, but the ether character and its origin is unknown. I also used MIL standard decoders, that pushed me closer to the problem solving, because the signal started to decipher, but I was unable to define, which MIL standard the Compositor (hacker) is using.

Of course, NPO Compositor can’t offer the solution, which can’t be certified because the transmission standard is undefined. But, the solution exists and already works on CP-6137-960FX server. There is the trend in musical and communication software to full-screen interfaces. For example, many routers goes with full-screen administration. Compositor RTOS was developed in that stream, that is why even user logging, which saved independently of session, comes in full-screen mode.

Another question is the routing table authorization in VLF network. Because, on a present date the emission of routing paths (tracks) of Exalted, Boosty and Perch projects were performed, the large contact base was aggregated. Then, considering the modern trend to digital and biometric passports, such authorization of 4795 routing tables can be considered as EU diplomatic passport. The legitimacy of such authorization is on question, but as an emission was done, bounded by the Royalty project, then no one prohibits the author to collect his own credits for his productions performance. That is why such activity is identical to running his own publishing company. That is why I decided to extend the NPO Compositor functionality to provide the services of routing paths (tracks) emission and collection of routing tables of equipment, which performed your productions. One emission will cost 150€ and will take about 4 hours 30 minutes with NPO Compositor equipment. You can book your own appointment on your production to return its original value in routing tables on the Compositor Software page in Facebook social network.

Ableton, Bessel beam, Boosty, Compositor, CP-6137-960FX, Digital Passport, Exalted, LASER, MDL12, NPO Compositor, Perch, Royalty, RTOS, vSwitch

May, 2019

By ruslany

Compositor project progress

A new usage for Compositor Software algorithm is found. Now, the time machine passes us to the far year 1989. Ruslan Yusipov was at NPO (Scientific Production Association) at that time and he saw the LASER machine for load tests there. Upsampling Compositor RTOS (Compositor v9 Hypervisor) up to 192 kHz (it was needed to make a physical build of the software and to upscale feeder working bands for that purpose), Ruslan Yusipov attained to 297.5 kHz feeder frequency, that coincides with that Soviet LASER working frequency. By this Ruslan Yusipov proved that feeders are on the constant injection threat on the lower frequencies, while the median shifts are minor at such high frequencies.

That machine consisted of two elements: the LASER itself and the propulsion stand with Earth and Moon models. Moreover, Moon was hardly attached to the Earth by metal kernel. That metal kernel has the spring cover, which measured the critical mass, when Moon orbited the Earth and takes in account its own rotations. LASER suited to pave the optimal course for taking on the Moon directly and without a trans-lunar injection. (Author remembers the words of I.V. Rozhdetstvenskiy)

Compositor RTOS is ideally suited for that purpose: it has auxiliary ether, aux channel, which depicts polarizer rotation. While, there is no need to create the whole interferential picture in aux channel, you can depict the valve cross-section and its 3-dimensional position.
Compositor (NASA and NSA ethical hacker)

For more information about virtual optical port read CP-6137-960FX server documentation.

Ruslan Yusipov task was to create a digital copy of the stand he saw at our NPO. The task was hard and had bureaucratic delays. But we are happy with the result at the moment.
NPO Compositor

How would this all aid the radio communications in XXI century? Compositor RTOS management information base is 4795 routing tables now, which increases NPO Compositor (Compositor Software) network, including trunks of new autonomous systems in it. Such direct communication between autonomous systems can be prohibited since the November 2019 on the Russian Federation territory. That is why this site will serve as the declaration for Roskomnadzor, because it is the only requirement, which they impose for Compositor software work on the territory of Russia. It also proves the fact that SASER SAS24P3L still accounted in the software registry of Ministry of Digital Development, Communications and Mass Media of the Russian Federation and the registry operator does the consistent work to support this software.

Compositor, CP-6137-960FX, LASER, NASA, RTOS, USSR

Tag : CP-6137-960FX

Niagara modem is disabled on the NPO Compositor server