infrastructure as a service vendors

 I am setting up the network in a building where some departments of Alura will work: Finance and Sales.

We could put the two departments on the same network, but with that we would have some problems:

Since all computers would be communicating by the same route, at the same time, the network could be slower;

One computer would be able to "see" the other. This could cause a malicious user to target some type of attack;

If any kind of problem occurred in any part of the network, both departments would be affected.

So we have to configure two different networks, each related to a department.

In a first approach, we can configure these physically separate networks. That is, with a switch for each department, as well as an interface on the router. However, the cost of this would be higher, since we would need more switches and a router with more ports.

Another way would be to logically separate the switch and the router, because that way, in addition to separating the network between departments, we are also saving money. This type of configuration is known asVLan.

Understanding VLans

VLans are nothing more than virtual local area networks (Lan). That is, they are logical networks configured in the samenetwork asset(routers and switches, for example). It is possible to divide our network into as many parts as we need for the project.

In addition to the division and economy of the network, we have the following advantages when implementing this type of network infrastructure as a service vendors:

More performance, as the broadcast domain it is divided between networks;

More security, only computers belonging to VLan can "see" each other;

We were able to better isolate the problems, as the networks are separate, the problem of one does not affect the other.

Nice, now that we know what a VLan is and how it can help us, how can we implement it in our network?