How to receive information if the Russian segment of the Internet is cut off from the global

More recently, the news “The Security Council wants to isolate Russia from the global Internet” was published , which alludes to several possible outcomes of the development (degradation) of the Russian segment of the Internet. Let's think about what these options are and how to live with it further.

Limitations

Two development options are possible:
1) Chinese;
2) North Korean;

With the first option, we will have a monitoring system for the entire Internet (except for P2P) and everything that does not meet the rules will be blocked.

The second option - on the contrary, implies a break in the physical connectivity of the Russian network with the foreign one.
Previously, no one could have thought that the Runet could go according to the second option, but at the moment it is he who is being implemented with some amendments.

Why the second option, and not the first?

The article published by the link above says that you need to be prepared for the fact that connectivity can disappear. In other words - if the same treasured button for disconnecting links is pressed, most of the resources within the country should work as before. It is quite obvious that a semi-autonomous system must be built.

Semi-autonomous system

This system, which should not depend on external DNS - several root (ROOT) DNSs have been installed in Russia for a long time, you can receive data from them (external DNS means where provider DNS sends requests for domain resolution).

In addition, 90% of the system’s resources should be available with disabled uplinks to civilized other countries.

Here are the top 25 resources in RU:

Almost all resources are located in Russia or use CDN, which is located in Russia (youtube, Vkontakte is building a CDN).

But the semi-autonomous system is “half” in that it should provide access to large Internet to legal entities during a certain procedure.

In other words, almost everything is ready for lowering the digital curtain.

But let's not panic. How to deal with it?

For a comprehensive fight, you need to have two weapons: P2P and the encrypted second level according to the OSI model.

When using P2P networks, all content is transferred from user to user, if without breaking links each person could receive content from abroad, now only a few can, but they will bring it to the network. As soon as this happens, within the network, this content will be synchronized with all devices on the network.

You can receive content across the border in several ways: two-way satellite Internet, (WI-FI / cable) bridges across the border with further wrapping in anonymous or pseudo-anonymous networks.

In other words, if suddenly the above scenario is implemented in Russia, then to install a channel for data transfer you will need:

1) Find a country with which we have no border and in which the Internet is freer - (the whole CIS);
2) Establish a connection to this country;
3) Wrap traffic between Russia <--> country in VPN / CJDNS;
4) Take the server abroad and make the following connection:

(For example, we take the server on UNIX in Europe, and as the donor country for the free Internet we mean Belarus)

UNIX server in EU <- CJDNS (TUNNEL) -> Belarus (server) <- CJDNS (WIFI bridge or wires) -> Resident of the nearest city in Russia <- CJDNS -> All other people who want to connect.

I want to remind you that the CJDNS protocol has dynamic routing, which means that there can be a lot of such holes and each hole will be:

1) Hide who made it from Belarus (if you go to a regular site through this tunnel, you will see the IP from the EU);
2) Hide intermediate resources, as they will not appear in direct routing (over IP);
3) Automatically balance the load;
4) No need to configure routing.

Why there will be many holes

"Holes" will be of various origins - based on enthusiasts - as I described above, as well as personal ones.

Not many people in the country will have access to the large web (for work), but those who have access will have access via SSH and VPN, and the traffic inside these protocols is encrypted, and no one bothers you with driving through this hole also other information.

I remind you of the popular OpenSource P2P projects that deserve your attention:

1) TOX - a messenger protected from wiretapping with audio / video communication - tox.im
2) Twister - P2P microblogging - ( Windows bundle \ Source code for building on other platforms) .