This article walks through Docker's built‑in networks, the four network modes (bridge, host, container, none), how to create and manage Linux network namespaces and veth pairs, and provides practical commands for configuring bridges, port mapping, DNS, and custom network settings.
This article explains Docker’s default bridge, host, and none networks, shows how containers on the same bridge can reach each other via IP or service name using Docker’s embedded DNS, demonstrates custom network creation for isolation, covers port mapping, host access, and troubleshooting techniques.
This article explains the limitations of existing intranet penetration tools, presents a custom SSH port‑mapping script, and provides a step‑by‑step tutorial on deploying FRP (frps and frpc), configuring tunnels, managing services with systemd, and verifying port forwarding through the FRP dashboard.
This guide explains Docker's three default networks, the four container network modes (bridge, container, host, none), how Linux bridges and veth pairs work, commands for network namespaces, port mapping, custom bridge creation, and practical examples for configuring Docker networking.
Learn how to make multiple Docker containers share a single external port by using reverse‑proxy load balancing with Nginx, configuring DNAT iptables rules, and leveraging the SO_REUSEPORT socket option, complete with step‑by‑step commands and network setup examples.
This guide explains how to configure port forwarding on both Windows and Linux servers using netsh and iptables, demonstrates temporary and permanent setups, and shows how to verify the mappings with curl in a multi‑machine lab environment.
This guide walks through configuring port mapping on Windows using netsh and on Linux using iptables, covering query, addition, deletion, enabling packet forwarding, NAT rules, a multi‑VM test environment, and verification with curl commands.
This guide explains step‑by‑step how to add, change, or remove port mappings for Docker containers by stopping the container, editing hostconfig.json (and optionally config.v2.json), and restarting the container, with commands for both Linux and Docker Desktop for Mac.
This article explains why home networks use private 192.168.x.x addresses, how NAT devices translate private to public IPs, the roles of SNAT and DNAT, the extension to NAPT with port translation, and techniques such as NAT traversal and hole punching that enable inbound connections from the Internet.
This guide explains Docker's built‑in network types, the four primary network modes (bridge, host, container, none), how the Docker bridge (docker0) works, how to create and manage Linux network namespaces, veth pairs, and custom bridge networks, plus practical commands for inspection and port mapping.
A Docker security flaw allows services bound to the loopback address with -p 127.0.0.1 to be reachable from external hosts due to an iptables rule, and the article explains the issue, demonstrates a proof‑of‑concept, and proposes tightened firewall rules as a fix.
A recent Docker security issue shows that publishing container ports to 127.0.0.1 does not prevent external access, because Docker adds an iptables rule that forwards traffic to the container’s internal IP, allowing attackers on the same network to reach the service.
A recent Hacker News discussion revealed that Docker’s iptables rule allows containers bound to 127.0.0.1 to be reachable from other hosts, and a step‑by‑step proof‑of‑concept demonstrates the issue while a revised iptables rule is proposed to enforce proper source‑address restrictions.
An exposed Docker security flaw allows services bound to 127.0.0.1 via the -p flag to be accessed externally through iptables rules, as demonstrated by a PostgreSQL container proof‑of‑concept, and the article proposes stricter iptables configurations and default localhost binding to mitigate the risk.
This article explains how computers communicate over the Internet, introduces switches to replace point‑to‑point cables, describes how LANs connect to form WANs, details IPv4 address structure, and shows how NAT and port mapping enable multiple devices to share a single public IP address.
This guide explains how Docker uses -p and -P options for port mapping, how to bind specific host IPs and protocols, view mappings, combine multiple bindings, and expose un‑mapped containers later via host iptables NAT rules for full network access.
