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

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

Restrictions

There are two options for development:
1) Chinese;
2) North Korean;

In the first version, we will create a monitoring system for the entire Internet (with the exception of P2P) and everything that does not satisfy 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 would have thought that the Runet could go on the second option, but at the moment it is he who is implemented with some amendments.

Why the second option, but not the first?

The article, published by the link above, says that you need to be prepared for the fact that connectedness can disappear. In other words, if that cherished button for disabling links is pressed, within the country most resources should work as before. It is quite obvious that it is necessary to build a semi-autonomous system.

Semi-autonomous system

This system, which should not be dependent on external DNS - several root (ROOT) DNS have long been established in Russia, you can receive data from them (by external DNS you mean where provider DNS send requests for domain resolution).

In addition, 90% of system resources should be available when uplinks are disabled to civilized other countries.

Here are the top 25 resources in RU:

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

But the semi-autonomous system is in fact “gender”, that it should provide access to the large Internet for legal entities when undergoing a certain procedure.

In other words, practically everything is already ready to lower 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 second level encrypted on the OSI model.

When using P2P networks, all content is transferred from user to user, if without a link break each person could receive content from abroad, now units will be able to, 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.

There are several methods to receive content across the border: 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 scenario described above 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) Connect to this country;
3) Wrap traffic between Russia <-> country in VPN / CJDNS;
4) Take a server abroad and make the following connection:

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

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

I want to remind 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 website through this tunnel, you will see the IP from the EU);
2) Hide intermediate resources, because they will not appear in direct routing (over IP);
3) Automatically balance load;
4) You will not need to configure routing.

Why there will be many holes

"Holes" will be of different origin - based on enthusiasts - as I described above, and personal.

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

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

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