chore: sync content to repo (#10168)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>
2026-09-24 15:00:31 +08:00 · 2026-07-22 10:41:23 +02:00
parent 3133d69109
commit 3e06ae7dd3
26 changed files with 29 additions and 29 deletions
@@ -1,5 +1,5 @@
 # Access Points
- 
+
 A wireless access point (AP) is a networking device that creates a Wi-Fi network by broadcasting a wireless signal and acting as a bridge between wireless clients and the wired network infrastructure. APs connect to the network via an Ethernet uplink to a switch and allow devices like laptops, phones, and tablets to join the network without a physical cable. In home environments, the AP function is typically built into the router, while in enterprise deployments, standalone APs are deployed throughout a building and managed either individually or through a centralized wireless controller.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # AP Placement & Coverage
- 
+
 AP placement is the process of determining the optimal physical location for access points to ensure complete wireless coverage across a space without dead zones or excessive overlap. Signal strength degrades with distance and is affected by physical obstacles like walls, floors, glass, and metal, so engineers must account for building materials and layout when planning deployments. Good AP placement balances coverage, capacity, and interference. Placing APs too far apart creates dead zones, while placing them too close causes co-channel interference that degrades performance for all connected devices.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Channel Planning
- 
+
 Channel planning is the process of assigning specific radio frequency channels to access points in a way that minimizes interference between them. In the 2.4 GHz band, only three non-overlapping channels (1, 6, and 11) are available, making careful planning essential in dense deployments. The 5 GHz band offers significantly more non-overlapping channels, giving engineers more flexibility. The goal of channel planning is to ensure that neighboring APs operate on different channels so their signals do not interfere with each other, which would otherwise reduce throughput and increase retransmissions across the network.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Channel Planning
- 
+
 Channel planning is the process of assigning specific radio frequency channels to access points in a way that minimizes interference between them. In the 2.4 GHz band, only three non-overlapping channels (1, 6, and 11) are available, making careful planning essential in dense deployments. The 5 GHz band offers significantly more non-overlapping channels, giving engineers more flexibility. The goal of channel planning is to ensure that neighboring APs operate on different channels so their signals do not interfere with each other, which would otherwise reduce throughput and increase retransmissions across the network.
@@ -1,5 +1,5 @@
 # Controllers
- 
+
 A wireless controller is a centralized device or software platform that manages multiple access points across a network from a single point of administration. Instead of configuring each AP individually, a controller lets engineers push configurations, monitor performance, manage roaming, and enforce security policies across the entire wireless infrastructure at once. Controllers can be hardware appliances installed on-premises, virtual machines running in a data center, or cloud-based platforms.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Design Best Practices
- 
+
 Network design best practices are a set of proven principles that engineers follow to build networks that are reliable, secure, and maintainable over time. Key practices include designing for redundancy at every layer to eliminate single points of failure, keeping the design as simple as possible since complexity increases the chance of misconfiguration and makes troubleshooting harder, segmenting the network using VLANs and subnets to limit broadcast domains and contain security incidents, documenting everything from IP address assignments to device configurations, and designing with scalability in mind so the network can grow without requiring a fundamental redesign. Following established frameworks like Cisco's PPDIOO (Prepare, Plan, Design, Implement, Operate, Optimize) lifecycle model provides a structured approach to network projects from initial planning through ongoing operation.

 Visit the following resources to learn more:
@@ -5,5 +5,5 @@ A load balancer is a device or software that distributes incoming network traffi
 Visit the following resources to learn more:

 - [@article@What is Network Load Balancing? Understanding Traffic Distribution](https://www.digitalocean.com/resources/articles/network-load-balancing)
- [@video@Load Balancer Explained](https://www.youtube.com/watch?v=1fN2UDbtGDQ)
- [@article@API gateway vs. Load balancer: Do you need one or both?](https://roadmap.sh/network-engineer/api-gateway-vs-load-balancer)
+- [@article@API gateway vs. Load balancer: Do you need one or both?](https://roadmap.sh/network-engineer/api-gateway-vs-load-balancer)
+- [@video@Load Balancer Explained](https://www.youtube.com/watch?v=1fN2UDbtGDQ)
@@ -1,5 +1,5 @@
 # LoRaWAN
- 
+
 LoRaWAN, or Long Range Wide Area Network, is a wireless communication protocol designed for IoT devices that need to transmit small amounts of data over very long distances while consuming minimal power. It operates in unlicensed sub-GHz radio bands and can achieve ranges of several kilometers in open environments, making it suitable for applications like smart meters, agricultural sensors, asset tracking, and environmental monitoring. LoRaWAN devices are typically battery-powered and designed to last years without replacement, prioritizing low power consumption and long range over speed, as data rates are intentionally very low.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # NAPALM
- 
+
 NAPALM, which stands for Network Automation and Programmability Abstraction Layer with Multivendor support, is an open-source Python library that provides a unified API for interacting with network devices from different vendors in a vendor-agnostic way. While Netmiko focuses on sending CLI commands and capturing output, NAPALM works at a higher level of abstraction. It can retrieve structured data like routing tables, interfaces, and BGP neighbors, and apply configuration changes in a consistent format regardless of whether the device is a Cisco IOS router, a Juniper device, or an Arista switch. NAPALM is particularly valued for its ability to validate configurations, compare desired versus actual state, and perform configuration rollbacks, making it a powerful tool for building reliable network automation workflows.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # NAT64
- 
+
 NAT64 is a transition mechanism that allows IPv6-only devices to communicate with IPv4-only servers and services by translating between the two address formats at the network boundary. As the Internet continues its gradual migration from IPv4 to IPv6, NAT64 bridges the gap during the transition period, ensuring that devices operating exclusively on IPv6 networks are not cut off from the large portion of the Internet that still runs on IPv4. It works in conjunction with DNS64, which synthesizes AAAA (IPv6) records for destinations that only have A (IPv4) records, allowing IPv6 clients to initiate connections to IPv4 destinations transparently.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # NETCONF
- 
+
 NETCONF, or Network Configuration Protocol, is a network management protocol designed specifically for configuring and retrieving the state of network devices. It uses XML to encode data and runs over SSH, providing a structured, transactional approach to device management that is far more reliable than screen-scraping CLI output. NETCONF supports operations like get, edit-config, copy-config, and commit, and works alongside YANG data models, which define the structure of the configuration data being exchanged, making it one of the primary protocols used in programmatic network management and automation.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Netmiko
- 
+
 Netmiko is an open-source Python library that simplifies SSH connections to network devices from multiple vendors, including Cisco, Juniper, Aruba, and many others. It handles the complexity of establishing SSH sessions, sending commands, and capturing output in a consistent way regardless of the underlying device type, eliminating the need to write custom connection code for each vendor. Netmiko is one of the most widely used Python libraries in network automation and is often the first tool network engineers learn when starting to automate CLI-based device interactions.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Network Design Principles
- 
+
 Network design principles are the guidelines and frameworks used to plan and build network infrastructure that is scalable, reliable, secure, and easy to manage. A well-designed network is not just about connecting devices; it is about making deliberate decisions about topology, redundancy, segmentation, and traffic flow so the network can grow and adapt over time without requiring a complete rebuild. Understanding design principles allows network engineers to evaluate tradeoffs, justify architectural decisions, and build networks that meet both current needs and future requirements.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # NFC
- 
+
 NFC, or Near Field Communication, is a short-range wireless communication technology that allows two devices to exchange small amounts of data when brought within a few centimeters of each other. It operates at 13.56 MHz and is most commonly used for contactless payments, access control cards, and quick device pairing. Unlike Wi-Fi or Bluetooth, NFC requires no manual pairing or configuration (proximity alone initiates the connection) making it ideal for fast, simple interactions where security through physical closeness is sufficient.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # PAT / NAT Overload
- 
+
 PAT, or Port Address Translation, also called NAT Overload, is the most common form of NAT used in home and enterprise networks. It allows many devices with private IP addresses to share a single public IP address simultaneously by tracking each connection using a unique combination of the public IP address and a port number. When a device on the internal network initiates a connection, the router assigns it a unique source port number and records the mapping in a translation table, using that mapping to correctly deliver return traffic back to the right internal device. This is what allows an entire office or household to access the Internet through a single public IP address.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Python for Networking
- 
+
 Python has become the dominant programming language in network engineering due to its simplicity, readability, and the rich ecosystem of libraries built specifically for interacting with network devices and infrastructure. Network engineers use Python to write scripts that automate configuration changes, parse device output, interact with APIs, process network data, and build custom tools. Libraries like Netmiko and NAPALM abstract away the complexity of connecting to and communicating with different vendors' devices, allowing engineers to write automation code without needing to handle low-level connection management themselves.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # RESTCONF
- 
+
 RESTCONF is a network management protocol that exposes the same YANG-modeled data as NETCONF but through a RESTful HTTP/HTTPS interface, making it more accessible to developers and tools already familiar with web APIs. Instead of XML over SSH, RESTCONF uses HTTP methods like GET, POST, PUT, PATCH, and DELETE, and supports both JSON and XML as data formats. It is easier to use and integrate than NETCONF for many automation use cases, though it lacks some of NETCONF's more advanced transactional features, making the two protocols complementary rather than direct replacements for each other.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Roaming & Band Steering
- 
+
 Roaming is the process by which a wireless client seamlessly transitions from one access point to another as it moves through a space, without dropping its network connection. In enterprise environments, fast roaming protocols like 802.11r (Fast BSS Transition) allow clients to re-authenticate quickly as they move between APs, which is critical for real-time applications like voice and video. Band steering is a related technique where the wireless controller or AP encourages dual-band capable devices to connect on the less congested 5 GHz band rather than the 2.4 GHz band, improving overall network performance by distributing clients more evenly across available spectrum.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Satellite
- 
+
 Satellite networking uses orbiting satellites to provide wireless connectivity to locations where terrestrial infrastructure is unavailable or impractical, such as remote areas, ships, and aircraft. Traditional geostationary (GEO) satellites orbit at approximately 36,000 km altitude, introducing significant latency (around 600ms round trip) that makes them unsuitable for real-time applications. Low Earth Orbit (LEO) satellite networks like Starlink orbit at 550–1,200 km, reducing latency to 20–60ms and offering speeds comparable to broadband Internet, making them increasingly viable as a primary or backup connectivity option for remote sites and as a redundant WAN link in enterprise network designs.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Spine-Leaf
- 
+
 Spine-leaf is a two-tier data center network architecture designed to provide consistent, low-latency connectivity between servers and storage in modern data centers. Every leaf switch connects to every spine switch, and no leaf connects directly to another leaf. All traffic between devices on different leaves passes through a spine switch in exactly two hops. This predictable, any-to-any connectivity pattern eliminates the bottlenecks and spanning tree complexity of traditional hierarchical designs, making spine-leaf the dominant architecture for hyperscale data centers, cloud environments, and any network carrying large volumes of east-west traffic between servers.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Static vs Dynamic NAT
- 
+
 Static NAT creates a permanent, one-to-one mapping between a specific private IP address and a specific public IP address, ensuring that a device always appears on the Internet with the same public IP. It is commonly used for servers that need to be consistently reachable from outside the network, such as web servers or mail servers hosted internally. Dynamic NAT, on the other hand, maps private IP addresses to public IP addresses from a pool on a first-come, first-served basis, with no device being guaranteed a specific public IP. Dynamic NAT is less common than PAT since it still requires one public IP per active connection, but is used in scenarios where full PAT is not suitable.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Three-Tier
- 
+
 The three-tier architecture organizes a network into three distinct layers: the core, distribution, and access layers. The core layer provides high-speed backbone connectivity between distribution blocks and is optimized purely for fast packet forwarding with no policy enforcement. The distribution layer handles routing, filtering, and policy between the core and access layers, while the access layer connects end-user devices to the network. This design is the traditional standard for large enterprise campus networks where scalability, redundancy, and clear separation of functions are critical.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Two-Tier
- 
+
 The two-tier architecture, also called the collapsed core design, organizes a network into two layers: the distribution layer and the access layer. The distribution layer handles routing, policy enforcement, and inter-VLAN communication, while the access layer connects end devices like computers, phones, and printers to the network. This design is simpler and more cost-effective than three-tier architectures and is well suited for small to medium-sized networks where a dedicated core layer would add unnecessary complexity and cost.

 Visit the following resources to learn more:
@@ -1,9 +1,9 @@
 # Wireless Site Surveys
- 
+
 A wireless site survey is the process of systematically assessing a physical environment before and after a wireless network deployment to determine optimal AP placement, identify sources of interference, and validate coverage. A passive survey involves walking the space with a Wi-Fi analyzer tool to measure existing signal strength and interference without connecting to any network. An active survey involves connecting to the network and measuring real throughput and performance across the space. Site surveys are standard practice before any enterprise wireless deployment and are used to produce heat maps that visually represent signal coverage and help justify AP placement decisions.

 Visit the following resources to learn more:

 - [@article@What is a Wireless Site Survey & What Types are There?](https://www.netally.com/tech-tips/what-is-a-wireless-site-survey/)
- [@video@Wireless Site Survey Checklist and Best Practices](https://www.parkplacetechnologies.com/blog/wireless-site-survey-checklist-best-practices/)
- [@article@How (and why) to perform a Wi-Fi Site Survey](https://www.youtube.com/watch?v=HdoMGb-ji1s)
+- [@article@How (and why) to perform a Wi-Fi Site Survey](https://www.youtube.com/watch?v=HdoMGb-ji1s)
+- [@video@Wireless Site Survey Checklist and Best Practices](https://www.parkplacetechnologies.com/blog/wireless-site-survey-checklist-best-practices/)
@@ -1,5 +1,5 @@
 # YANG
- 
+
 YANG is a data modeling language used to define the structure, syntax, and semantics of the data that network devices exchange through management protocols like NETCONF and RESTCONF. It describes exactly what configuration and operational data a device supports in a way that both humans and machines can understand. YANG models are the foundation of modern network automation: before a script or tool can configure a device via NETCONF or RESTCONF, it needs to know the YANG model for that device to understand how to structure its requests correctly.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Zigbee & Z-Wave
- 
+
 Zigbee and Z-Wave are low-power, short-range wireless communication protocols designed primarily for IoT and smart home devices such as sensors, lights, locks, and thermostats. Both operate on mesh network topologies where devices can relay signals through each other to extend range, making them well suited for environments with many small, battery-powered devices spread across a space. Zigbee operates in the 2.4 GHz band and is an open standard, while Z-Wave operates in sub-GHz frequencies (around 900 MHz) and is managed by a single industry alliance. Both are widely used in home automation and building management systems.

 Visit the following resources to learn more: