Repository navigation
fix(gateway): warn when a peer gateway's address is in this node's pool - #1606
Merged
Merged
Conversation
kvinwang
enabled auto-merge
November 18, 2026 08:51
Signed-off-by: Kevin Wang <wy721@qq.com>
kvinwang
force-pushed
the
fix/gateway-warn-pool-overlap
branch
from
November 18, 2026 10:21
5bf985a to
435ea85
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cross-node agreement on instances assumes no node's client pool contains another node's gateway address, but config validation only sees the local node. When node info is loaded (startup and node changes), warn once per peer whose replicated
wg_ipthis node could hand to a CVM. Log only; nothing is refused and no record format changes. Broadcast and reserved nets of peers are not replicated, so they stay unchecked.From the Lean model of allocation (#1597,
IpAlloc.lean,PoolsClear).