YueGuobin b17d021bf6

fix: derive per-node IOL app id so linked routers get distinct MACs ...

IOL derives interface MACs from its application ID. With a constant
local-app every node shared the same MACs, and linked routers dropped
each other's frames as MAC loops — ARP never resolved and pings were
100% lost even though the whole uBridge datapath was forwarding.

Derive local-app from the node UUID (stable across restarts, kept in
1..1022) and align remote-app with the netiomux convention CML uses
(1023). Verified end to end: two iol-xe nodes, Ethernet0/0 link,
ARP resolves both ways, ping 4/5 (first loss = ARP), graceful
stop/start keeps the NVRAM config.

2026-09-05 21:54:51 +08:00

..

resources

docs: document the BusyBox ifup CIDR trap in the docker init path

2026-08-28 23:26:24 +08:00

__init__.py

feat: add IOL (iol-runner) Docker node support

2026-09-05 21:54:12 +08:00

docker_error.py

fix(docker): handle container name conflict automatically

2026-07-13 09:57:55 +02:00

docker_vm.py

feat: model IOL adapters as 4-port units like the IOU node type

2026-09-05 21:54:51 +08:00

iol_docker_vm.py

fix: derive per-node IOL app id so linked routers get distinct MACs

2026-09-05 21:54:51 +08:00

vendor_docker_vm.py

feat: model IOL adapters as 4-port units like the IOU node type

2026-09-05 21:54:51 +08:00