chore: sync content to repo (#9986)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>
2026-10-24 23:06:33 +08:00 · 2026-05-18 18:34:28 +02:00
parent b5dfdb9ada
commit 78b86207ff
40 changed files with 42 additions and 42 deletions
@@ -1,5 +1,5 @@
 # ACLs
- 
+
 ACLs, or Access Control Lists, are ordered sets of rules applied to a router or switch interface that permit or deny traffic based on criteria such as source IP address, destination IP address, protocol, and port number. They are one of the most fundamental tools for controlling traffic flow and enforcing security policies on a network. ACLs can be applied inbound or outbound on an interface and are evaluated sequentially, with the first matching rule determining the action taken on the packet.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Ansible
- 
+
 Ansible is an open-source automation tool that uses simple, human-readable YAML files called playbooks to automate the configuration and management of servers, network devices, and cloud infrastructure. Unlike some automation tools, Ansible is agentless — it communicates with devices directly over SSH or APIs without requiring any software to be installed on the target device first. For network engineers, Ansible is particularly valuable for pushing configuration changes to many routers and switches simultaneously, ensuring consistency across the network and eliminating the need to log into each device manually.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # AWS
- 
+
 AWS (Amazon Web Services) offers a comprehensive set of networking services that allow engineers to build and manage network infrastructure entirely in the cloud. Core networking components include VPC (Virtual Private Cloud) for creating isolated virtual networks, subnets for segmenting those networks, Security Groups and Network ACLs for controlling traffic, Route Tables for directing traffic between subnets and to the Internet, and Internet Gateways for enabling public connectivity. For connecting cloud and on-premises environments, AWS provides services like Direct Connect for dedicated private connections, AWS VPN for encrypted tunnels, Transit Gateway for connecting multiple VPCs and on-premises networks at scale, and Elastic Load Balancing for distributing traffic across resources.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Azure
- 
+
 Microsoft Azure provides a full suite of networking services built around the concept of Virtual Networks (VNets), which are the foundational isolated network environments where Azure resources are deployed. Key networking services include VNet Peering for connecting virtual networks together, Azure VPN Gateway for site-to-site and point-to-site VPN connections, ExpressRoute for dedicated private connectivity between on-premises networks and Azure, Azure Firewall for centralized network security, Network Security Groups (NSGs) for controlling inbound and outbound traffic, and Azure Load Balancer and Application Gateway for distributing traffic across services. Azure also offers Azure Virtual WAN for large-scale branch connectivity and Azure DNS for managing domain name resolution within and across cloud environments.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Cloud Network Types
- 
+
 Cloud providers offer several types of virtual network constructs that mirror traditional networking concepts but operate in software. The most fundamental is the Virtual Private Cloud (VPC), a logically isolated section of the cloud where resources are deployed. Within a VPC, public subnets host resources accessible from the Internet, while private subnets contain resources with no direct public exposure. Cloud environments also support concepts like peering connections between VPCs, transit networks for hub-and-spoke architectures, and overlay networks for connecting cloud resources across regions or providers.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Cloud Networking Basics
- 
+
 Cloud networking refers to the networking infrastructure and services delivered through cloud platforms, allowing organizations to build, connect, and secure their resources in the cloud using virtual equivalents of traditional network components. Instead of physical routers, switches, and firewalls, cloud networking uses software-defined resources that can be provisioned, configured, and scaled through APIs and web consoles. Understanding cloud networking is increasingly essential for network engineers as more infrastructure moves away from on-premises data centers and into cloud environments.

 Visit the following resources to learn more:
@@ -1,6 +1,6 @@
 # Cloud Routing
- 
-Cloud routing refers to how traffic is directed between subnets, virtual networks, on-premises environments, and the Internet within a cloud platform. Each cloud provider uses route tables  (collections of rules that determine where traffic destined for specific IP ranges should be sent) to control the flow of packets through the virtual network. Cloud routing also involves dynamic routing protocols through services like AWS Transit Gateway, Azure Route Server, or GCP Cloud Router, which use BGP to exchange routes automatically between cloud and on-premises environments, making large hybrid network architectures manageable without manual route configuration.
+
+Cloud routing refers to how traffic is directed between subnets, virtual networks, on-premises environments, and the Internet within a cloud platform. Each cloud provider uses route tables (collections of rules that determine where traffic destined for specific IP ranges should be sent) to control the flow of packets through the virtual network. Cloud routing also involves dynamic routing protocols through services like AWS Transit Gateway, Azure Route Server, or GCP Cloud Router, which use BGP to exchange routes automatically between cloud and on-premises environments, making large hybrid network architectures manageable without manual route configuration.

 Visit the following resources to learn more:

@@ -1,5 +1,5 @@
 # Cloud VPN
- 
+
 A Cloud VPN is a managed service offered by cloud providers that creates encrypted IPSec tunnels between a cloud virtual network and an on-premises network or another cloud environment over the public Internet. It allows organizations to securely extend their private network into the cloud without needing a dedicated physical connection, making it a cost-effective option for hybrid connectivity. Cloud VPNs are suitable for moderate traffic volumes and scenarios where the latency and variability of the public Internet are acceptable, as opposed to dedicated interconnect services that provide more consistent, higher-bandwidth private connections.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Common Network Issues
- 
+
 Common network issues are recurring problems that network engineers encounter regularly across different environments and infrastructures. These include IP address conflicts where two devices share the same address, DNS resolution failures where domain names cannot be translated to IP addresses, default gateway misconfigurations that prevent traffic from leaving the local network, duplex and speed mismatches between connected devices causing performance degradation, VLAN misconfigurations that isolate devices unintentionally, routing loops where packets cycle endlessly between routers, and high latency or packet loss caused by congestion, faulty hardware, or misconfigured QoS policies.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Datadog
- 
+
 Datadog is a cloud-based observability platform that provides monitoring, logging, and security capabilities across infrastructure, applications, and networks in a single unified interface. It collects metrics, traces, and logs from servers, containers, cloud services, and network devices, correlating them to give a complete picture of system health. For network engineers, Datadog offers network performance monitoring (NPM) features that provide visibility into traffic flows, latency between services, and the health of network paths across on-premises and cloud environments.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Dynatrace
- 
+
 Dynatrace is an AI-powered observability platform that automatically discovers, maps, and monitors the full technology stack, from infrastructure and networks to applications and user experience. Its standout feature is the Davis AI engine, which automatically detects anomalies, determines root causes, and reduces alert noise by correlating data across the entire environment. While primarily used by application and platform teams, network engineers in large enterprises use Dynatrace to gain visibility into how network performance impacts application behavior and end-user experience.
@@ -1,5 +1,5 @@
 # GCP
- 
+
 Google Cloud Platform (GCP) takes a unique approach to networking with its globally distributed Virtual Private Cloud (VPC), which, unlike AWS and Azure, operates as a single global resource rather than being tied to a specific region. Key networking services include Cloud Router for dynamic routing between on-premises and GCP networks using BGP, Cloud VPN and Cloud Interconnect for hybrid connectivity, Cloud Load Balancing for distributing traffic globally across regions, Firewall Rules for controlling traffic at the network level, and Cloud DNS for scalable domain name resolution. GCP's network is built on the same private global fiber infrastructure that powers Google's own services, giving it a performance advantage for traffic that can be routed through Google's backbone rather than the public Internet.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # GLBP
- 
+
 GLBP, or Gateway Load Balancing Protocol, is a Cisco proprietary protocol that goes beyond simple redundancy by also distributing traffic across multiple routers simultaneously. Unlike HSRP and VRRP, where only one router actively handles traffic at a time, GLBP allows all routers in the group to forward traffic, improving both availability and bandwidth utilization. Each router in the group shares the same virtual IP address but is assigned a different virtual MAC address, allowing traffic to be load-balanced across all active gateways.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Grafana
- 
+
 Grafana is an open-source data visualization and dashboarding platform that connects to a wide range of data sources, including Prometheus, InfluxDB, Elasticsearch, and SNMP collectors, and displays the data in customizable, real-time dashboards. In network engineering, it is commonly used to visualize metrics like interface traffic, packet loss, latency, and device health collected from monitoring tools. Grafana does not collect data itself but excels at making complex time-series data understandable through graphs, gauges, and alerts.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # GRE / IPSec Tunnels
- 
+
 GRE, or Generic Routing Encapsulation, is a tunneling protocol that wraps packets from one protocol inside packets of another, allowing traffic to be carried across networks that would not normally support it. On its own, GRE provides no encryption, so it is commonly combined with IPSec, which adds authentication and encryption to secure the tunnel. Together, GRE over IPSec is widely used to create flexible, secure connections between sites while supporting routing protocols and multicast traffic that plain IPSec tunnels cannot carry on their own.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # HSRP
- 
+
 HSRP, or Hot Standby Router Protocol, is a Cisco proprietary protocol that provides gateway redundancy by allowing two or more routers to work together as a single virtual router. One router acts as the active gateway handling all traffic, while one or more standby routers monitor it and take over automatically if the active router fails. End devices are configured to use the shared virtual IP address as their default gateway, so they experience no disruption when a failover occurs.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Infrastructure as Code
- 
+
 Infrastructure as Code (IaC) is the practice of managing and provisioning infrastructure — including networks, servers, and cloud resources — through machine-readable configuration files rather than manual processes or interactive tools. Instead of clicking through a web console or typing commands into a CLI to set up a network, IaC lets you write code that describes exactly what the infrastructure should look like, check that code into version control, and apply it automatically and repeatably. This brings software development practices like version control, code review, and automated testing to infrastructure management, making changes more reliable, auditable, and consistent across environments

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # ipconfig / ifconfig
- 
+
 ipconfig (on Windows) and ifconfig (on Linux and macOS) are command-line tools used to view and manage the network configuration of a device's interfaces. They display information such as the assigned IP address, subnet mask, default gateway, and MAC address for each network adapter. They are among the first tools used when troubleshooting a connectivity issue at the device level, confirming whether the device has a valid network configuration.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Linux for Networking
- 
+
 Linux is the operating system that powers the majority of the world's network infrastructure, from routers and firewalls to servers and cloud platforms. Network engineers working with Linux need to understand how to configure network interfaces, manage routing tables, control firewall rules, monitor traffic, and automate tasks through the command line. Unlike GUI-based systems, Linux gives engineers direct, low-level control over every aspect of network behavior, making it an essential skill for anyone working in modern networking environments.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Load Balancing
- 
+
 Cloud load balancing distributes incoming network traffic across multiple backend resources, such as virtual machines, containers, or serverless functions, to ensure no single resource is overwhelmed and that applications remain available even if individual components fail. Unlike hardware load balancers in traditional data centers, cloud load balancers are fully managed services that scale automatically with traffic and require no physical maintenance. Cloud providers offer multiple types, including application load balancers that operate at Layer 7 and make routing decisions based on HTTP content, and network load balancers that operate at Layer 4 for high-performance, low-latency traffic distribution.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Troubleshooting Methodologies
- 
+
 A troubleshooting methodology is a structured approach to diagnosing network problems that prevents guesswork and reduces time to resolution. The most common approaches are bottom-up (starting at the Physical layer and working up through the OSI model), top-down (starting at the Application layer and working down), and divide and conquer (starting at a middle layer based on available evidence). Most methodologies follow a general cycle: identify the problem, establish a theory of probable cause, test the theory, create a plan of action, implement the fix, verify full functionality, and document the outcome.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # MPLS VPN
- 
+
 MPLS VPN is a technique that uses Multiprotocol Label Switching to create private, isolated network connections over a shared provider backbone. Service providers use it to offer private WAN connectivity to enterprise customers, where each customer's traffic is logically separated from others, even though it travels across the same physical infrastructure. MPLS VPNs are highly scalable and offer predictable performance, making them a popular choice for connecting multiple branch offices across a wide area network.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # netstat
- 
+
 netstat, short for network statistics, is a command-line tool that displays active network connections, listening ports, routing tables, and network interface statistics on a device. It is useful for identifying which services are listening on which ports, spotting unexpected or unauthorized connections, and understanding the current state of network activity on a machine. Although largely replaced by the newer `ss` command on Linux systems, netstat remains widely used and available across Windows, macOS, and Linux.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Network Automation
- 
+
 Network automation is the process of using software, scripts, and tools to automatically configure, manage, monitor, and operate network devices and infrastructure instead of performing these tasks manually. Traditionally, network engineers would log into each device individually and type commands one at a time — a process that is slow, error-prone, and impossible to scale across hundreds or thousands of devices. Automation replaces repetitive manual work with code that can apply consistent configurations across the entire network in seconds, respond to events without human intervention, and make infrastructure changes as reliable and repeatable as software deployments.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # nslookup
- 
+
 nslookup is a command-line tool used to query DNS servers and retrieve information about domain name resolution. It allows a network engineer to check what IP address a domain resolves to, which DNS server is being used, and whether DNS records such as A, MX, or CNAME entries are correctly configured. It is an essential tool for diagnosing DNS-related issues, such as a website being unreachable due to a missing or incorrect DNS record.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Packet Analysis
- 
+
 Packet analysis is the process of capturing and inspecting the raw data packets traveling across a network to understand exactly what is happening at a detailed level. By examining individual packets, network engineers can diagnose connectivity issues, identify security threats, verify that protocols are behaving correctly, and understand the root cause of performance problems. Tools like Wireshark and tcpdump are the primary instruments used for packet analysis, allowing engineers to filter, decode, and interpret traffic at every layer of the OSI model.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # ping
- 
+
 ping is one of the most basic and widely used network diagnostic tools, sending ICMP Echo Request packets to a target host and measuring whether a response is received and how long it takes. It is typically the first tool used when troubleshooting connectivity, quickly confirming whether a device is reachable on the network. The results show round-trip time and packet loss, giving an immediate indication of whether a path exists between two devices and how stable it is.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Prometheus
- 
+
 Prometheus is an open-source monitoring and alerting toolkit originally built at SoundCloud and now widely adopted across the industry. It collects metrics by scraping data from configured targets at regular intervals, stores them in a time-series database, and provides a powerful query language called PromQL to analyze and visualize the data. While not network-specific, Prometheus is commonly used in modern infrastructure to monitor network devices, services, and applications, often paired with Grafana for visualization and alerting.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # SD-WAN
- 
+
 SD-WAN, or Software-Defined Wide Area Network, is a technology that uses software to centrally manage and optimize how traffic is routed across multiple WAN connections, such as MPLS, broadband Internet, and 4G/5G links, based on real-time conditions and application requirements. Instead of rigidly sending all traffic through a single expensive MPLS circuit, SD-WAN can intelligently distribute traffic across the best available link at any given moment, improving performance and reducing costs. It is managed through a centralized controller that gives network engineers visibility and control over the entire WAN from a single interface, without needing to manually configure each individual device at every site.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Security Groups
- 
+
 Security groups are virtual firewalls applied at the resource level in cloud environments, controlling which traffic is allowed to reach individual instances, containers, or services based on rules that specify protocol, port range, and source or destination IP address. Unlike traditional network firewalls that sit at the perimeter, security groups travel with the resource and enforce rules wherever that resource is deployed within the cloud. Most cloud providers implement security groups as stateful, meaning if an inbound connection is allowed, the corresponding outbound response is automatically permitted without needing an explicit outbound rule.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Shell & Scripting
- 
+
 The shell is the command-line interface used to interact with a Linux system, while scripting is the practice of combining shell commands into reusable files called scripts. For network engineers, shell scripting helps automate repetitive tasks such as backing up device configurations, parsing log files, running diagnostic checks across multiple devices, and generating reports. Bash is the most common shell used in networking environments, and even basic scripting knowledge can significantly reduce manual work and human error. Python is equally important and has become the dominant programming language in network engineering. Compared to Bash, Python is better suited for complex automation tasks and serves as the foundation for many modern network automation tools and frameworks, including Ansible and API-based network management.

 Visit the following resources to learn more:
@@ -1,6 +1,6 @@
 # speedtest
- 
-A speedtest is a diagnostic tool that measures the actual throughput of a network connection by downloading and uploading data to a remote server and reporting the results in megabits per second. It is used to verify that a connection is delivering the bandwidth expected from an ISP or internal network link, and to identify discrepancies between advertised and real-world speeds. Speedtest tools like Speedtest.net or iPerf (used internally between two endpoints) are common first steps when users report slow Internet or network performance.
+
+A speedtest is a diagnostic tool that measures the actual throughput of a network connection by downloading and uploading data to a remote server and reporting the results in megabits per second. It is used to verify that a connection is delivering the bandwidth expected from an ISP or internal network link, and to identify discrepancies between advertised and real-world speeds. Speedtest tools like [Speedtest.net](http://Speedtest.net) or iPerf (used internally between two endpoints) are common first steps when users report slow Internet or network performance.

 Visit the following resources to learn more:

@@ -1,5 +1,5 @@
 # Terraform
- 
+
 Terraform is an open-source Infrastructure as Code tool developed by HashiCorp that allows engineers to define and provision infrastructure — including network resources — using a declarative configuration language called HCL (HashiCorp Configuration Language). Instead of manually creating networks, subnets, firewall rules, and load balancers through a cloud console, Terraform lets you describe the desired state of your infrastructure in code and then automatically creates or modifies resources to match that state. It supports all major cloud providers and many network vendors, making it a popular choice for managing cloud networking infrastructure consistently and repeatably.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # traceroute / tracert
- 
+
 traceroute (on Linux and macOS) and tracert (on Windows) are diagnostic tools that map the path packets take from a source device to a destination, showing each hop along the route and the latency at each one. By sending packets with incrementally increasing TTL (Time to Live) values, they reveal every router the traffic passes through on its way to the target. This makes them invaluable for identifying where in the network a problem is occurring — whether a packet is being dropped, a specific hop has high latency, or traffic is taking an unexpected route.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Traffic Management
- 
+
 Traffic management refers to the set of techniques and tools used to control how network traffic flows, ensuring efficient use of available bandwidth and reliable delivery of data. It covers everything from prioritizing critical applications over less important ones, to shaping traffic to prevent congestion, to distributing load across multiple servers or links. Effective traffic management ensures that the network performs well under normal conditions and degrades gracefully under heavy load.
@@ -1,5 +1,5 @@
 # Troubleshooting
- 
+
 Network troubleshooting is the process of identifying, diagnosing, and resolving problems that affect network connectivity, performance, or reliability. It requires a combination of systematic methodology, knowledge of networking concepts, and familiarity with diagnostic tools. Good troubleshooting is not about randomly trying fixes, it is about gathering evidence, forming a hypothesis, testing it, and working through the problem layer by layer until the root cause is found and resolved.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Virtual Networks
- 
+
 A virtual network in cloud computing is a software-defined network that replicates the functionality of a physical network entirely in software, allowing cloud resources to communicate with each other, with on-premises systems, and with the Internet. Virtual networks are defined through configuration rather than physical cabling, making them fast to create, easy to modify, and infinitely scalable. Each cloud provider has its own implementation —AWS calls it a VPC, Azure calls it a VNet, and GCP also uses the VPC model— but all share the same core concept of providing isolated, configurable network environments for cloud resources.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # VRFs
- 
+
 VRF, or Virtual Routing and Forwarding, is a technology that allows a single physical router to run multiple independent routing tables at the same time. Each VRF acts like a completely separate virtual router, meaning traffic in one VRF is fully isolated from traffic in another, even if they share the same physical hardware. This is commonly used by service providers to keep customer traffic separate on shared infrastructure, and by enterprises to isolate different departments or network segments on the same device.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # VRRP
- 
+
 VRRP, or Virtual Router Redundancy Protocol, is an open standard protocol that provides the same gateway redundancy function as HSRP but works across equipment from any vendor. A group of routers share a virtual IP address, with one elected as the master and the others as backups ready to take over if the master becomes unavailable. Because it is vendor-neutral, VRRP is the preferred choice in multi-vendor network environments.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # VXLAN
- 
+
 VXLAN, or Virtual Extensible LAN, is a network virtualization technology that extends Layer 2 networks over a Layer 3 infrastructure by encapsulating Ethernet frames inside UDP packets. It was created to overcome the scalability limitations of traditional VLANs, which support a maximum of 4,096 network segments, by supporting up to 16 million virtual network identifiers. VXLAN is widely used in data centers and cloud environments where large numbers of isolated virtual networks need to coexist on shared physical infrastructure.

 Visit the following resources to learn more: