bind address
The network address a server listens on, which decides who can connect to it.
In more detail
Binding to 127.0.0.1 accepts only local connections, while 0.0.0.0 accepts connections on every network interface. A server listening only on 127.0.0.1 cannot be reached from other machines or containers.
Examples
--kafka-addr 0.0.0.0:9092A service bound to 127.0.0.1 accepts only connections from the same machine; bound to the wildcard 0.0.0.0 it accepts them on every interface. Two services can share a port on different addresses, but a wildcard bind claims the port everywhere. When a local check works but remote clients fail, inspect the bind address before touching firewall rules.local=127.0.0.1 host=only any=0.0.0.0 host=all contrasts a loopback bind with a wildcard bind.Related terms
- localhost — The name a machine uses for itself; traffic sent there never leaves that machine.
- port publishing — Forwarding a port on the host to a port inside a container so the service can be reached from outside.
- network interface — A connection point, real or virtual, through which a machine or container sends and receives network traffic.
- --kafka-addr — The Redpanda start flag that sets the address and port the broker listens on for Kafka clients.
- port — A number from 1 to 65535 that picks out one service on a machine, such as 22 for SSH or 80 for plain web traffic.
- listening socket — A socket that has claimed a local address and port and is waiting to accept incoming connections.
Taught in
- Run The Spine Service And Publish Its Port — Docker Architecture & Production Containers
- Port Publishing, Localhost And Network Troubleshooting — Docker Architecture & Production Containers
- Development Overrides, Hot Reloading And Debuggers — Docker Architecture & Production Containers
- Why A Log And Not A Queue — Apache Kafka & Event Streaming
- Ports, Sockets And What Listening Means — Linux Fundamentals & Systems Administration