Files
moby/libnetwork
Rob Murray 9a6e96fd9c Before sending ARPs/NAs, check the bridge is ready
We don't enable STP on bridges belonging to bridge networks,
but bridge ports still need to transition from "disabled" to
"forwarding", after the veth device comes "up". Until then,
the bridge will just drop packets.

So, if a container's network is a veth device, and its other
end is slaved to a bridge - wait for the bridge port to
be "forwarding".

Signed-off-by: Rob Murray <rob.murray@docker.com>
2025-01-30 20:40:01 +00:00
..
2025-01-20 10:10:51 +01:00
2024-09-06 21:53:09 +10:00
2024-11-12 14:02:09 +01:00
2024-11-11 18:19:04 +08:00
2024-06-27 23:18:48 +02:00
2024-09-06 21:53:09 +10:00
2024-09-06 21:53:09 +10:00
2025-01-27 14:19:19 +01:00
2024-06-27 23:18:48 +02:00
2025-01-27 14:19:19 +01:00
2024-09-06 21:53:09 +10:00
2024-11-12 14:02:09 +01:00

libnetwork - networking for containers

Libnetwork provides a native Go implementation for connecting containers

The goal of libnetwork is to deliver a robust Container Network Model that provides a consistent programming interface and the required network abstractions for applications.

Design

Please refer to the design for more information.

Using libnetwork

There are many networking solutions available to suit a broad range of use-cases. libnetwork uses a driver / plugin model to support all of these solutions while abstracting the complexity of the driver implementations by exposing a simple and consistent Network Model to users.

Contributing

Want to hack on libnetwork? Docker's contributions guidelines apply.

Code and documentation copyright 2015 Docker, inc. Code released under the Apache 2.0 license. Docs released under Creative commons.