Download "ViPNet #10: Координаторы | Создание и настройка в ЦУС"

"videoThumbnail ViPNet #10: Координаторы | Создание и настройка в ЦУС

Модификатор Mirror в Blender. Урок

Модификатор Mirror в Blender. Урок

Channel: Про ИЗО

3Ds Max. Урок 1. Создание стен в 3DMax

3Ds Max. Урок 1. Создание стен в 3DMax

Channel: Уроки 3Ds Max от Ильи Изотова

Кубик Рубика. Часть 1. Массив (Array) (Урок по 3ds Max для новичков)

Кубик Рубика. Часть 1. Массив (Array) (Урок по 3ds Max для новичков)

Channel: RENDERSTORM I Уроки 3Ds Max

[UNITY] На чем делать онлайн игри? Что с UNET в 2021?

[UNITY] На чем делать онлайн игри? Что с UNET в 2021?

Channel: Vasa «/» - уроки по розробці на Unity.

ViPNet #5: Выбор модели координатора

ViPNet #5: Выбор модели координатора

Channel: mr.Marshanskiy

SolidWorks. Библиотеки (базы) материалов: создание, установка и настройка

SolidWorks. Библиотеки (базы) материалов: создание, установка и настройка

Channel: Solid Andrey

[Урок 4.3.2} Редактирование ландшафта - Modes Landscape Sculpt | Unreal Engine4

[Урок 4.3.2} Редактирование ландшафта - Modes Landscape Sculpt | Unreal Engine4

Channel: Cyberstars - How to create a game

ViPNet #9: УКЦ | Обзор интерфейса и функционала

ViPNet #9: УКЦ | Обзор интерфейса и функционала

Channel: mr.Marshanskiy

🌧 🎧 #10 Сладкий шум дождя 10 часов 🌦 Звуки для сна. Белый шум Черный экран 🔔 Сладкий шум 😴

🌧 🎧 #10 Сладкий шум дождя 10 часов 🌦 Звуки для сна. Белый шум Черный экран 🔔 Сладкий шум 😴

Channel: Сладкий Шум

ViPNet #7: Создание Администратора сети, дистрибутивов ключей + установка ключей

ViPNet #7: Создание Администратора сети, дистрибутивов ключей + установка ключей

Channel: mr.Marshanskiy

mr.Marshanskiy

все о vipnet

випнет

vipnet

vip net

проектирование и администрирование защищенных сетей ViPNet

клиент

координатор

скзи

coordinator

vpn

сеть випнет

шифрование

криптозащита

курс

кардинатор

вип нет

hw

создание админа сети

создание

администратор сети

создание дистрибутива

ключи

цус

vipnet administrator

моя сеть

параметры

настройки

часть 10

№10

#10

координаторы

создание и настройка в цус

00:00:01

coordinators, how to create them in the

00:00:03

network control center, what settings do

00:00:05

coordinators have, but let’s start with

00:00:07

coordinators, which means they are created in our

00:00:10

network control center in the

00:00:13

coordinators section, in order to create a

00:00:15

coordinator, click on the new

00:00:17

coordinator button, a window opens, give

00:00:21

some name any mode of operation

00:00:24

by default for now the main one we

00:00:27

will have performs the functions of a vpn server, that

00:00:31

is, this is the standard purpose of

00:00:33

its coordinator, and we also

00:00:35

leave the checkbox to create a user of the same name

00:00:38

on a new node and

00:00:40

automatically, that is, together with the building of a

00:00:42

network node, that is, we have a coordinator a

00:00:48

Balzac will also be created in the users section, which will be registered with this

00:00:50

coordinator, but I suggest that you immediately

00:00:53

check the configure box after

00:00:55

creation.

00:00:57

In this case, we are creating a

00:01:00

coordinator, so it appears in our

00:01:02

list and now the coordinator properties window has opened,

00:01:05

but let’s go in

00:01:06

order in the main parameters we can

00:01:10

give a name and some

00:01:12

additional description right away I want to say that from

00:01:15

the description but essentially nothing depends, that

00:01:18

is, the search engine here that

00:01:20

is there will not work according to the description, it

00:01:24

works only by name, this is worth

00:01:27

taking into account coordinators without the VPN server function We

00:01:31

’ll leave it for now and go to the clients section. As you can see now, there’s

00:01:35

nothing in the clients section,

00:01:38

so for the test I propose to

00:01:41

create several clients behind this

00:01:43

coordinator,

00:01:52

and so I created three clients that were

00:01:56

registered specifically for the coordinator,

00:01:58

which I also just created and will

00:02:00

also create again some other

00:02:02

coordinator

00:02:08

and I’ll do the same thing with

00:02:09

several clients and register them with the

00:02:12

new coordinator second,

00:02:17

that is, now he

00:02:19

will eat 3 clients that

00:02:21

are registered with coordinator 1 and 3

00:02:23

clients with coordinator 2, but it

00:02:25

will be more convenient to explain this way, and so

00:02:27

we move on to the properties of coordinator one

00:02:30

client and

00:02:32

in the clients section we can see

00:02:34

which clients have been registered and on

00:02:37

this coordinators, that is, for which

00:02:40

clients our coordinator acts as a

00:02:42

connection server.

00:02:44

We go further with connections with nodes. By default,

00:02:47

connections are created with the network administrator and

00:02:50

also with clients that were

00:02:53

registered with this coordinator.

00:02:55

here if we open this window we can

00:02:58

see the status of the connection that the

00:03:01

administrator has a blocked

00:03:03

connection, this means that this connection cannot be

00:03:05

deleted and it was created automatically.

00:03:09

As for other clients, there are

00:03:11

several reasons for

00:03:13

automatic communication; firstly, this is the connection

00:03:16

between the node and its coordinator and there is no connection

00:03:19

between the node and the IP address server by

00:03:22

default yet, let's move

00:03:25

on if there are groups on the network,

00:03:28

here you can add connections with the entire

00:03:31

user group at once in the users section there

00:03:35

is an automatically created

00:03:38

user which we created again

00:03:41

at the very beginning, but if necessary

00:03:44

you can create an additional

00:03:46

user, for example, let’s go like this to

00:03:49

create users

00:03:52

and select the network node under which it

00:03:55

will be registered, namely our

00:03:57

coordinator one, create it

00:04:00

and now I’ll go to the properties of

00:04:02

coordinator one again in users and see

00:04:05

that there are now two users behind it, the same

00:04:07

thing can be done and with

00:04:09

clients, yes, therefore, there is such a possibility,

00:04:12

it’s just worth taking into account,

00:04:15

but from here, by the way, we can either delete

00:04:18

if necessary, in this case, to

00:04:22

coordinators, and indeed there is

00:04:25

only one user left, and

00:04:27

but from the users from the

00:04:29

users tab, this user was not deleted

00:04:32

if it is no longer needed you will have to

00:04:35

manually delete it from the users section,

00:04:37

click on the red cross and delete the world

00:04:41

server channels as for inter-

00:04:45

server channels, now this section is

00:04:47

empty and this is basically logical because

00:04:51

if we go first to the connection, we will not

00:04:55

see any of the coordinators here, but let me

00:04:58

remind you coordinators Essentially, these are nodes

00:05:01

that are connected to each other, and it is the

00:05:03

connections between coordinators that create paths

00:05:06

for end nodes to clients, so in

00:05:11

this case, if we try to click

00:05:15

my network and check the network configuration,

00:05:18

conflicting data will be detected,

00:05:22

namely the following error:

00:05:25

unconnected network segments detected, now it

00:05:28

shows that there are three segments in the network, the

00:05:31

first segment is the central

00:05:32

coordinator, the second segment is

00:05:35

coordinators 1 and 3, segment coordinator 2,

00:05:39

that is, now we have three

00:05:42

independent points up to three nodes and they are

00:05:45

not connected in any way; in principle, one

00:05:49

would think that if we

00:05:51

take this so let's move on in connection with the

00:05:53

nodes to add a connection with the central

00:05:58

coordinator, yes we have a connection,

00:06:02

it would seem that

00:06:04

everything needs to work, but if we do the

00:06:07

same thing, check the network configuration, it will

00:06:11

be discovered that we still have

00:06:13

three segments left,

00:06:15

this happens for the reason that The connections

00:06:18

that we organize are only a logical

00:06:21

connection, but in order for us to be

00:06:24

organized from one coordinator

00:06:26

to another, roughly speaking, a backbone must be

00:06:28

organized; that’s why

00:06:31

we have a section between server channels and

00:06:34

now we add the

00:06:37

central coordinator here,

00:06:41

check the configuration and see that there are already

00:06:43

only two segments left in one

00:06:46

segments already united central

00:06:48

coordinators coordinator 1 and the second

00:06:51

separate coordinator 2 we can make a

00:06:54

star from our network in this case we will

00:06:57

go to the central coordinator

00:06:59

for example we will also go to the world of server

00:07:02

channels and here we will add 2 coordinator

00:07:06

we will add everything in this case we check

00:07:11

the configuration and there are no conflicts and now our

00:07:15

coordinator one will see

00:07:16

coordinator 2 through the central

00:07:19

coordinators, that is, we will have a

00:07:20

star topology, but to make a

00:07:23

triangle we go, for example, to

00:07:25

coordinator 2,

00:07:26

add a world server channel with

00:07:29

coordinator 1 and now we

00:07:31

have a triangle Thus,

00:07:33

through an inter-server channel we are building

00:07:37

precisely highways along which it is already possible

00:07:40

to organize logical connections and in

00:07:45

the future it will be clear which

00:07:48

route the traffic will take. There is also a

00:07:51

section on Internet channels and for now this

00:07:54

section is empty because this section

00:07:57

concerns trusted networks for which

00:08:00

the coordinator is the gateway for you, that is,

00:08:03

if briefly looking ahead, we have

00:08:06

trusted networks and where we have, well,

00:08:09

other vipnet networks, for example, and that on the

00:08:12

one hand and on the other hand a

00:08:14

gateway coordinator is selected, that is, such a

00:08:17

coordinator through which

00:08:19

all traffic intended for

00:08:21

third parties will flow networks, but also in fact, and precisely

00:08:24

in this section,

00:08:25

internetwork channels, and for example, for the

00:08:28

central coordinator, since in our country it

00:08:31

is the central coordinator who acts as the

00:08:33

gateway for third-party networks, and here there

00:08:36

is information just for which

00:08:40

networks and he acts as the gateway for you, it’s just a

00:08:42

tautology on a tautology but nevertheless, let's move on,

00:08:45

and now we have the default node roles,

00:08:48

again this is set by

00:08:50

the settings mind,

00:08:52

the role is applied when creating a

00:08:54

coordinator, namely the software weeping

00:08:57

coordinator, that is, we have the

00:08:59

doctor's software

00:09:01

installed on the operating system

00:09:03

and here he is, our software coordinator,

00:09:07

but nevertheless, we can choose for ourselves

00:09:09

what role it will have now if we

00:09:13

try to add a role, for example,

00:09:16

make this coordinator not a software

00:09:19

and hardware software-hardware

00:09:21

complex, but we will not see anything here for

00:09:23

the reason that we have already defined a

00:09:26

software vpn coordinator,

00:09:28

so for first we select all the roles

00:09:31

necessary

00:09:32

and in our case this is

00:09:34

file messaging and a software weepin'

00:09:36

coordinator and delete after that

00:09:41

we add and will now we have a choice of

00:09:46

which coordinator

00:09:49

this network node will be

00:09:50

or whether we have a software and hardware

00:09:53

complex for the entire process or Swede 1000

00:09:56

we can also make it virtual in our case,

00:09:58

but either leave it programmatic when

00:10:01

choosing a role, here again it is worth clearly

00:10:03

understanding that we are now simply selecting

00:10:06

roles in the network control center when

00:10:10

we issue a key distribution for

00:10:12

this coordinator inside the dst file, that

00:10:16

is, inside the distribution keys there will be

00:10:18

hardwired information that this file

00:10:21

is intended specifically for the platform as much as

00:10:24

1000 and if we try to install the dst file

00:10:27

on the piece of hardware as much as 100 seconds,

00:10:30

then the piece of hardware will curse and won’t let us

00:10:33

install the key and say that it’s not a

00:10:35

suitable platform, so here it’s worth

00:10:39

understanding that if we we create a network

00:10:42

node in the form of a coordinator for as much as 100 sec, then we

00:10:45

must set our weight pc in our

00:10:48

case, I will leave the role for it as much as 100 sec

00:10:51

because I’m installing it anyway, I wo

00:10:53

n’t go anywhere yet, but just for example, let it

00:10:55

be like this and so these The

00:10:58

sections that we looked at here

00:11:00

contain information about the network node, in

00:11:03

principle, in one of the previous videos,

00:11:06

again, I showed how coordinators are installed,

00:11:08

how the client is installed,

00:11:10

and there we issued a distribution of keys,

00:11:14

carried out the initial initialization of these

00:11:17

keys at the final workplace, be it a

00:11:20

coordinator, be it a vipnet client and In

00:11:24

this initial initialization,

00:11:27

some of the

00:11:31

initial parameters are set on the Steve node; these

00:11:34

initial parameters are

00:11:35

determined in the network control center,

00:11:38

then, in principle, some parameters

00:11:41

can be changed manually from under the administrator

00:11:43

on the

00:11:44

end node, but these are the primary

00:11:48

data are entered precisely in the

00:11:51

network control center and that's all we

00:11:52

looked at the main parameters clients that the

00:11:55

coordinator has what

00:11:57

connections what inter-server channels this is all

00:12:00

necessary for the coordinator himself on

00:12:03

which these keys will be installed

00:12:06

with such information so that the coordinator

00:12:08

understands who he has connections with whom does

00:12:11

it generally interact, what is its

00:12:13

role, and so on, this information is also

00:12:15

necessary for other network nodes

00:12:17

so that they also understand that, for example,

00:12:20

when creating a coordinator,

00:12:22

that first of all this coordinator appeared on the network,

00:12:24

that this is a coordinator

00:12:27

who has exactly this, for example,

00:12:29

the identifier is called exactly this

00:12:32

so that is, all these parameters are

00:12:34

needed both by the client himself, that is, these

00:12:37

parameters were needed both by the

00:12:39

coordinator himself and the entire network as a whole, but the

00:12:42

next

00:12:44

address parameter in external networks may seem

00:12:47

that if we add an IP address, it will

00:12:49

automatically

00:12:51

tune in to the coordinators, but no, this is not so, in fact, we are

00:12:53

here defining the stove makers who supposedly

00:12:56

exist on coordinators simply for the

00:12:59

rest of the network when setting up a

00:13:00

coordinator, in theory, everyone

00:13:04

should already know which stove makers

00:13:06

will hang on the coordinators, and if its

00:13:08

stove makers are already known,

00:13:10

I suggest adding them here, they are

00:13:13

indicated here simple and the stove maker even without a

00:13:16

mask, please note the mask is not even

00:13:18

indicated simply and the address is for example

00:13:21

some white one and the stove maker is like

00:13:23

this, supposedly white and the stove maker and the whole

00:13:25

mask is not even indicated, I suggest

00:13:27

also checking this box,

00:13:29

use IP address to access m

00:13:31

ftp

00:13:32

you are here so as not to rewrite it manually,

00:13:34

you can select the interface that supposedly

00:13:37

we will have, this is the external interface, it’s clear,

00:13:39

yes, because it is white and stove and

00:13:41

use ftp for it,

00:13:43

as you can see, information is automatically driven here

00:13:45

m ftp, let me briefly remind you, it

00:13:48

is necessary in order to exchange

00:13:50

service information in order pass

00:13:53

through business mail as well; this applies to the

00:13:56

coordinator and letters via business mail,

00:13:58

but in general, business traffic

00:14:00

is passed through precisely thanks to the

00:14:03

ftp module. Thus, as soon as we

00:14:06

have added a coordinator, all other

00:14:08

clients are coordinators that are in one way or

00:14:10

another connected with this

00:14:13

coordinator that we are setting up they

00:14:15

will know, regardless of what is

00:14:18

happening now, whether the coordinators are

00:14:20

turned on or off,

00:14:21

they will assume that this is why

00:14:24

the IP address can be

00:14:27

contacted, if we don’t indicate the address here,

00:14:29

then not a single network node that is

00:14:32

again connected to this coordinator

00:14:34

will understand but how to access it in general,

00:14:37

that is, the network node will

00:14:41

know that a coordinator exists, it

00:14:44

has certain settings, certain

00:14:46

communication roles,

00:14:47

but he doesn’t know how to get to it, what stove makers to

00:14:50

use, but we wo

00:14:53

n’t dwell on this in detail for now

00:14:55

and will just move on again, in

00:14:58

one of the next videos I will show in more

00:15:01

detail,

00:15:02

but for now let’s go to the firewall settings

00:15:04

in the firewall settings

00:15:07

we have several configurations with

00:15:09

static address translation with

00:15:11

dynamic address translation and a

00:15:13

coordinator as a

00:15:15

firewall if we don’t already have a firewall

00:15:20

yes I either the coordinator himself acts

00:15:22

as a firewall or access to

00:15:25

the coordinator is not blocked in any way, then we

00:15:27

can simply not use it and at the same time

00:15:29

we check the box to use this pi

00:15:31

tunnel, I suggest removing it a little

00:15:34

later we will touch on the principles

00:15:36

of routing

00:15:37

in vipnet networks for now it is important to understand

00:15:40

what is visible then the traffic still

00:15:43

works, I sing, etc.

00:15:44

Finding a tunnel is used only

00:15:46

if it is not possible to establish a session of the same

00:15:49

type, in this case, this type of pi

00:15:51

si si rises and as soon as the connection is established along this type of pi,

00:15:54

the type is

00:15:56

collapsed and returns again and

00:15:58

Oedipus in general, again, we will

00:16:01

analyze all this a little later, but nevertheless less

00:16:04

if we don’t use a firewall,

00:16:06

then in the addresses we should have at

00:16:10

least white and pechnik here and the network node

00:16:12

will directly go along white and pechnik

00:16:15

unian but which we will use I

00:16:17

won’t change here,

00:16:19

but let’s briefly summarize the

00:16:21

firewall settings here we determine

00:16:23

how exactly the network nodes

00:16:26

will be able to reach this

00:16:28

coordinator,

00:16:29

and in fact, it is by setting up the

00:16:31

firewall that it

00:16:33

is determined how the network will generally

00:16:37

function stably and unstable,

00:16:39

how often the network nodes will fall off, how

00:16:41

often the coordinator will be available,

00:16:43

that is, the settings to knead it into the screen

00:16:45

need to be paid attention to special attention because

00:16:48

this is very important, but for now let’s move on to the

00:16:50

clients’ firewall; in fact,

00:16:53

clients have the same

00:16:56

firewall settings, we will also touch on it,

00:16:58

but for convenience, in principle, we can

00:17:02

do this: in the

00:17:05

clients’ firewall settings, we select for example what the

00:17:08

client will simply use

00:17:11

dynamic address translation, okay, and

00:17:16

all the following clients that

00:17:18

register with this coordinator

00:17:21

will be written like this in their firewall settings

00:17:24

by default according to the

00:17:26

server parameters of the clients’ IP addresses, and

00:17:29

in our case

00:17:31

this coordinator acts as

00:17:34

the server IP addresses and

00:17:36

therefore the client will use

00:17:39

dynamic address translation,

00:17:42

but for now let’s move on to the next tab and

00:17:44

this is tunneling, which means we

00:17:47

have network nodes, this is a coordinator and a

00:17:50

vipnet client, but also how do we know that

00:17:53

clients and coordinators have a

00:17:56

traffic encryption function? It is from

00:17:58

this network node that encryption already begins,

00:18:00

but there are some servers and

00:18:02

or ordinary machines on which the vipnet

00:18:04

client is not installed, and at the same time there is

00:18:07

the possibility of tunneling the bus and

00:18:10

encryption in this case it will

00:18:13

start from the coordinator, in fact,

00:18:16

this setting is

00:18:17

probably exactly this setting rules like

00:18:21

5 was to eat for example until about

00:18:23

something similar if we add here

00:18:26

for example and pi address or range of

00:18:28

addresses

00:18:29

let's some kind of IP address from the

00:18:31

internal network add a

00:18:36

predator in the tunnel but also firstly after

00:18:38

this setup all network nodes that

00:18:40

have a connection with this the coordinator that

00:18:43

we are setting up, they will have information

00:18:45

that behind this coordinator there is an

00:18:49

IRU tunnel and my machine with these my

00:18:51

stove-makers, and this in turn means

00:18:53

that we have a marching under the

00:18:56

end

00:18:57

network node through this coordinator

00:19:01

that we are setting up before its tunnel

00:19:03

ruim of her machine, so we

00:19:05

configure vpn between network nodes,

00:19:08

for example, and the coordinator, then the encrypted traffic

00:19:13

to the coordinators is decrypted and

00:19:16

sent in unencrypted form to

00:19:19

this IP address and in the opposite direction,

00:19:21

approximately the same thing happens,

00:19:23

unencrypted traffic comes from this and the

00:19:25

stove maker to the coordinator with the

00:19:28

traffic is encrypted by the coordinator and sent via Weber

00:19:32

to the final network node, but if, for

00:19:35

example, from the internal network with the IP address

00:19:38

they are 10 10 10 10 and for example 10 10 10 100

00:19:41

a request comes, then in this case

00:19:45

the coordinator will check his list of

00:19:48

panels and see that this IP address is 10 10

00:19:51

10 100 gets into the list and it will simply

00:19:54

block the packet and will not

00:19:56

encrypt it or send it anywhere, it will

00:19:58

simply block it stupidly, similarly

00:20:00

if the packet somehow arrives on the

00:20:03

external network before this

00:20:05

coordinator, but the destination

00:20:08

will be an IP address not included in

00:20:11

this list and either the ranges it

00:20:15

will block it in the same way, so

00:20:17

when adding IP addresses to the list

00:20:19

of tunnels, we firstly allow

00:20:23

traffic to pass through this coordinator

00:20:26

from just such a stove-maker or to such an

00:20:29

IP address. This is the first, but the second is the

00:20:33

creation of routes on network nodes

00:20:36

that are connected with the coordinator that

00:20:39

it is through this coordinator that

00:20:41

you can get to this IP address;

00:20:43

also about the settings of the coordinator there is also a

00:20:46

DNS server for the wins server and but to be honest,

00:20:48

I haven’t worked with this and haven’t

00:20:51

encountered it so for now I won’t

00:20:54

say anything about it and they won’t for now

00:20:56

I won’t tell you what I don’t know,

00:20:58

let’s say now let’s imagine that we

00:21:00

have set up a coordinator, we

00:21:02

have all configured it correctly, we have added all the connections,

00:21:05

configured the IP address of the tunnel, we have

00:21:08

configured everything, and then essentially the

00:21:11

administration procedure is simple, we have an

00:21:14

excellent keyboard shortcut kontrol g and we

00:21:19

can create all directories for the

00:21:21

entire list at once we create and it will stop the

00:21:24

status is expected keys keys let me remind you that we

00:21:27

issue network nodes in the key certification center

00:21:30

section,

00:21:32

here he is our coordinator who we

00:21:35

changed now the status of the keys here

00:21:38

we need to create a distribution of keys when

00:21:41

creating a network node

00:21:42

we will need in any case

00:21:44

perform primary initialization and for

00:21:49

this we must have a key distribution kit

00:21:51

and therefore the tooth of the

00:21:54

key certification center and we need to

00:21:56

create it here this is what is done as

00:22:00

we already discussed

00:22:03

in the last video you deliver the key

00:22:05

center you can create an admin password for the

00:22:08

coordinator I especially advise you to

00:22:10

do this for the coordinator, create an

00:22:12

admin password because it is the

00:22:14

coordinators who most often have to

00:22:16

make some changes, this is all

00:22:19

done through the admin, so we create an

00:22:21

admin password,

00:22:22

indicate the password expiration date and

00:22:26

then right-click and issue a new

00:22:30

key distribution,

00:22:32

select the authentication method, for example, the

00:22:35

default password and everything opens a

00:22:39

folder with key distribution kits, here it is

00:22:41

our coordinator 1 and inside our file with the

00:22:45

dst extension, this dst file

00:22:48

will need to be loaded if we have a

00:22:52

software coordinator there and double-

00:22:54

click

00:22:55

to install it, if we have a

00:22:57

hardware and software complex,

00:22:59

then in one of them again in the following videos I

00:23:02

will show how this is done there,

00:23:04

when initializing the keys,

00:23:07

this file is also selected,

00:23:08

that is, the algorithm is basically similar

00:23:10

to just program coordinates, of course

00:23:14

on Windows it’s especially easy to do it,

00:23:16

double-click on the file installed and everything is

00:23:18

ready, the only thing worth remembering here is that

00:23:22

after we issued a

00:23:24

distribution of keys, but we

00:23:28

made changes to the network, and the coordinator was

00:23:30

connected to other coordinators,

00:23:32

connections were organized between servers,

00:23:35

and therefore we seemed to issue a distribution of

00:23:39

keys, but

00:23:42

we have not made any changes for the entire network yet; in addition, we

00:23:45

also have these clients created for

00:23:48

them, it is also necessary to create

00:23:49

distribution kits of keys,

00:23:51

but here we will see that for example, for a

00:23:53

central coordinator that already

00:23:55

existed, you just need to

00:23:58

create a key, and we will do this like this:

00:24:01

create and transfer the keys taste, that is,

00:24:05

you can right-click with the mouse right away with

00:24:08

Shift for example, select two at once,

00:24:10

you need to create a key and right-click

00:24:12

or the combination of keys kontrol and

00:24:15

and we see that these keys were transferred

00:24:19

taste we return to the ace send to

00:24:24

the directory keys send to the directory

00:24:26

enable or the combination of keys kontrol

00:24:29

forest and we see that we can send

00:24:32

an update and at this moment as

00:24:35

soon as the updates were sent, this

00:24:38

means that these are the changes that

00:24:40

we made, yes, we created a

00:24:42

coordinator, gave it settings,

00:24:45

organized a world server channel with the

00:24:47

central coordinator, added connections with it,

00:24:51

these are all the changes that you

00:24:54

made that relate specifically to the

00:24:56

central coordinator, they were

00:24:59

and sent to the compartment and when the

00:25:01

central coordinator accepts the updates,

00:25:04

his configuration is updated, the

00:25:07

communication list is updated, the list of inter-

00:25:09

server channels is updated, he sees that there is a

00:25:12

new coordinator with whom his

00:25:14

channel is organized, but in fact, this is exactly

00:25:18

how the update occurs on the network,

00:25:20

namely by creating directories by

00:25:23

creating keys and sending these

00:25:26

updates to network nodes and, in principle,

00:25:29

this algorithm applies not only to

00:25:31

coordinators but also to VIP

00:25:33

clients, but overall it’s excellent, I think the

00:25:37

video is good and it came out, I hope

00:25:39

everything was clear, if it’s not clear,

00:25:41

please comment in the cart, if you

00:25:45

wish, you can subscribe to the channel if you haven't

00:25:48

already done so,

00:25:49

well, I'm not saying goodbye,

00:25:52

see you soon, see you soon on new videos bye

Description:

Изучение раздела Координаторы в ЦУС, а также создание и настройка сетевых узлов Координаторы. https://t.me/mr_Marshanskiy - Канал в Телеграмм, чтоб не пропускать плюшки https://t.me/mr_M_chat - Чат для вопросов и обсуждения ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ПОДДЕРЖИ АВТОРА: https://money.yandex.ru/to/410013576120595 - Яндекс.Деньги https://www.donationalerts.com/r/mrmarshanskiy - Донатики ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Привет! Образовательный контент сейчас не особо популярен, намного проще смотреть всякую дичь, но я уверен, что лучше меньший объем, но с лучшим качеством, а главное - с полезным направлением. Поэтому, если считаете видео полезным и достойным для просмотра другими, не поскупитесь любым способом поддержать: лайком, комментарием, а если поделитесь с друзьями - будет вообще шикарно. Это даже важнее денег будет:) Успеха! Группа в ВК - https://vk.com/mr.marshanskiy Группа в Telegram - https://t.me/eveng_rus #mrMarshanskiy

Preparing download options

Popular

HD video

Only sound

All

* — If the video is playing in a new tab, go to it, then right-click on the video and select "Save video as..."

** — Link intended for online playback in specialized players

Questions about downloading video

How can I download "ViPNet #10: Координаторы | Создание и настройка в ЦУС" video?

http://unidownloader.com/ website is the best way to download a video or a separate audio track if you want to do without installing programs and extensions.
The UDL Helper extension is a convenient button that is seamlessly integrated into YouTube, Instagram and OK.ru sites for fast content download.
UDL Client program (for Windows) is the most powerful solution that supports more than 900 websites, social networks and video hosting sites, as well as any video quality that is available in the source.
UDL Lite is a really convenient way to access a website from your mobile device. With its help, you can easily download videos directly to your smartphone.

Which format of "ViPNet #10: Координаторы | Создание и настройка в ЦУС" video should I choose?

The best quality formats are FullHD (1080p), 2K (1440p), 4K (2160p) and 8K (4320p). The higher the resolution of your screen, the higher the video quality should be. However, there are other factors to consider: download speed, amount of free space, and device performance during playback.

Why does my computer freeze when loading a "ViPNet #10: Координаторы | Создание и настройка в ЦУС" video?

The browser/computer should not freeze completely! If this happens, please report it with a link to the video. Sometimes videos cannot be downloaded directly in a suitable format, so we have added the ability to convert the file to the desired format. In some cases, this process may actively use computer resources.

How can I download "ViPNet #10: Координаторы | Создание и настройка в ЦУС" video to my phone?

You can download a video to your smartphone using the website or the PWA application UDL Lite. It is also possible to send a download link via QR code using the UDL Helper extension.

How can I download an audio track (music) to MP3 "ViPNet #10: Координаторы | Создание и настройка в ЦУС"?

The most convenient way is to use the UDL Client program, which supports converting video to MP3 format. In some cases, MP3 can also be downloaded through the UDL Helper extension.

How can I save a frame from a video "ViPNet #10: Координаторы | Создание и настройка в ЦУС"?

This feature is available in the UDL Helper extension. Make sure that "Show the video snapshot button" is checked in the settings. A camera icon should appear in the lower right corner of the player to the left of the "Settings" icon. When you click on it, the current frame from the video will be saved to your computer in JPEG format.

What's the price of all this stuff?

It costs nothing. Our services are absolutely free for all users. There are no PRO subscriptions, no restrictions on the number or maximum length of downloaded videos.