YueGuobin 37d7b9121e

feat(docker): wire Docker-to-Docker links through a kernel bridge ...

Eligible links (both endpoints Docker, same compute, no filters/markers,
stopped nodes, no unix-socket NIO containers) are wired as veth pairs
enslaved into a per-link Linux kernel bridge (gns3 + 11 hex of the link
id, filling IFNAMSIZ) instead of the uBridge UDP relay, so frames flow
entirely in the kernel.

- NIOBridge NIO type: the controller decides the datapath in
  UDPLink._prepare and both computes enslave their deterministic gv*/gc*
  veth pair via uBridge's docker/brctl modules
- carrier/suspend = host-end admin state; both endpoints race-safely
  create/delete the bridge (EEXIST/EBUSY/ENOENT tolerated)
- veth adapters can still attach relay (UDP) links on a running node:
  lazy relay bridge over AF_PACKET on the host end (add_nio_ethernet)
- filters/markers/capture are rejected with explicit errors on this
  datapath (they live in the uBridge relay); vendor unix-socket
  containers are excluded; Server.enable_kernel_datapath is the
  kill-switch (default on)
- host-end veths survive container death and are removed on stop plus
  swept by name on the next start (crash/stale recovery)

2026-10-06 00:21:07 +08:00

..

routes

feat(docker): wire Docker-to-Docker links through a kernel bridge

2026-10-06 00:21:07 +08:00

__init__.py

Move endpoints to routes & preparations to use a database.

2020-11-19 15:21:03 +10:30

server.py

style: sort imports in agent and remaining compute modules

2026-10-02 12:43:26 +03:00