When an agent restarted with multiple networks (e.g. hexor and ultradesu),
Agent::reserve_range() previously attempted to reserve the default configured
range (10.13.37.0/24) for whichever network happened to be listed first in
storage, even if that network had already agreed upon a different range
(such as 10.79.175.0/24). As a result, the first network seized 10.13.37.0/24
in the route table, causing the second network (which genuinely used 10.13.37.0/24)
to trigger a spurious RouteError::Overlap warning at startup until the first
network asynchronously loaded its signed records and released the reservation.
Key changes:
- In crates/tsunagi/src/agent/mod.rs, make reserve_range asynchronous and
inspect stored signed records first using StateSet::agreed_range().
- If an agreed range already exists in storage, reserve that specific range
in routes immediately instead of preemptively claiming the default
overlay_ipv4_range.
Validation on Linux:
- cargo fmt --all -- --check passed.
- cargo clippy --locked --workspace --all-targets -- -D warnings passed.
- cargo test --locked --workspace --all-targets --jobs 2 -- --test-threads=2 passed (349 tests passed).
Aleksandr Bogomiakov
46575d0899