Política de Privacidade

  Revisão 07/2023 CONDIÇÕES E TERMOS DE SERVIÇO E UTILIZAÇÃO “Intelligence Software” A Intelligence Software provê serviços de desenvolvimento de aplicativos no território brasileiro. Temos a responsabilidade de proteger cada cliente e lhes proporcionar os melhores serviços possíveis. As diretrizes seguintes foram projetadas para assegurar a qualidade de nossos serviços. Tenha certeza de que entendeu e concorda com as políticas, pois a violação dessas políticas poderá resultar em suspensão ou término da sua conta sem direito a reembolso de valores pagos. Você confirma e concorda que a Intelligence Software, a seu absoluto e exclusivo critério, pode alterar ou modificar este Acordo, e quaisquer políticas ou acordos integrados a ele, a qualquer momento, e tais alterações ou modificações entrarão em vigor imediatamente após a publicação neste Site, e seu uso deste Site ou dos Serviços encontrados neste Site após tais alterações ou modificações terem...
Postar um comentário

Ethernet switches - Book Review

Today's tip is another book that I read a week or two ago and it's about ethernet switches, that device full of ports to connect different devices. Anyway, it's an extremely short book, about 90 pages, and it gives an overview of the main themes of switches. Talk a little about vlans, how to use switches and what they are for, spanning tree, stacking, cascading, what to consider when buying switch equipment, such as workload, port speed, purpose and possible problems. It's a valid read and gives a general idea about switches.

 

 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Comentários

Postar um comentário

Postagens mais visitadas deste blog

Phoenix Project - Review

Imagem
Hello, how is everything? I come today to bring a tip from a book and the tip is the book "Phoenix Project".       I was looking for something more practical to comment and relate to the application that I'm making available on the Play Store, "Plan - Governança e gestão de TI". I had already heard about this book but I hadn't taken the time to dedicate myself to it so I read it and it's really a very good book, I recommend it to anyone in the field who wants some tips on management, governance, DevOps and still others. The DevOps part deserves special attention because as it is said in the book this is a watershed, there is another book by the same author is the DevOps Handbook, I intend to read it in a while. About the book Phoenix Project, here are some points that he talks about and that add a lot to the reader and that for those who already have some knowledge in the area, they will identify and relate to good practices already known and which are p...
Leia mais

List of features to be realized in Packet Tracer

Below is a list of what can be done in Packet tracer as a lab and learning , some functionalities may need to be performed in another network simulator such as GNS3 for example :   - PVST+ - CDP - RADIUS - PPP - PAP and CHAP authentication - Static routes - Etherchannel - LACP and PAgP - VLANs - Hostname/Passwords - Telnet - SSH - Port Security - serial connection - VTP - STP - EIGRP - OSPF - RIP - access-list - NAT - Static/Dynamic - PAT - Hub and Spoke - Inter VLAN routing - DHCP server - IPv6 - HSRP - VRRP - IPSec - Netflow - DNS Server - Email server - web server - PPPoE -DR and BDR - Backup conf files - traceroute - Ping - Modify cost of a link - FTP - Dual FSM - GRE over IPSec - RIPng - GRE - VLSM - Unicast/Broadcast/Multicast - Examine ART table - TFTP - Wireless LAN - BGP - iBGP/eBGP - MPLS
Leia mais

Understanding static routing

Imagem
Understanding the routing process is essential for any professional who wants to work with networks so let's consider the initial scenario below. We are going to talk in this post about static routing, which is the basis for understanding dynamic routing, using protocols such as OSPF.       In the figure above we have three computers "PC1, PC2 and PC3" and we also have three routers "R1, R2 and R3". We will need to define five networks as shown in the image below. Note that interfaces 1 and 2 of each of the routers are also identified.       Now we can define the IPs according to the following information: PC1 - 192.168.0.10/24 R1 - Interface 1 - 192.168.0.1/24 PC2 - 192.168.1.10/24 R3 - Interface 2 - 192.168.1.1/24 PC3 - 192.168.2.10/24 R2 - Interface 3 - 192.168.2.1/24   Defined the networks where the PCs are, we are now going to define the link networks where IPs were saved and that is why the /30 mask was used.   R1 - Interface 2 - 192.168.11...
Leia mais