infrastructure//Docker//subnet

A subnet is a range of IP addresses, and Docker networks use private ranges (typically 172.x.x.x) separate from the host LAN (192.168.x.x). That is why a host at `192.168.1.50` and a container at `172.18.0.5` coexist without conflict: they sit on different virtual networks. The host LAN and the Docker network are parallel, isolated layers, and port mapping is the only bridge between them.

A subnet is a range of IP addresses, and Docker networks use private ranges (typically 172.x.x.x) separate from the host LAN (192.168.x.x). That is why a host at 192.168.1.50 and a container at 172.18.0.5 coexist without conflict: they sit on different virtual networks. The host LAN and the Docker network are parallel, isolated layers, and port mapping is the only bridge between them.

In CIDR notation, 176.45.0.0/16 means the first 16 bits are the network (176.45) and the remaining 16 bits the host (10.2 in 176.45.10.2). A /16 gives 65534 usable host addresses, plenty for development networks.