amery/jpictl
2
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

rings: fix NodeZeroMax/NodeMax to not accept .255

Browse Source 
Signed-off-by: Alejandro Mery <amery@jpi.io>
This commit is contained in:
Alejandro Mery
2024-06-02 22:06:45 +00:00
parent f4b837f3e0
commit bb40f395d9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
pkg/rings/rings.go
+2 -2
View File
@@ -16,10 +16,10 @@ const (
// ZoneMax indicates the highest number that can be used for a [ZoneID]. // ZoneMax indicates the highest number that can be used for a [ZoneID].
ZoneMax = (1 << 4) - 1 ZoneMax = (1 << 4) - 1
// NodeMax indicates the highest number that can be used for a [NodeID]. // NodeMax indicates the highest number that can be used for a [NodeID].
NodeMax = (1 << 12) - 1 NodeMax = (1 << 12) - 2
// NodeZeroMax indicates the highest number that can be used for a [NodeID] // NodeZeroMax indicates the highest number that can be used for a [NodeID]
// when its a gateway connected to Ring 0 (backbone). // when its a gateway connected to Ring 0 (backbone).
NodeZeroMax = (1 << 8) - 1 NodeZeroMax = (1 << 8) - 2
// RingZeroBits indicates the size of the prefix on the ring 0 (backbone) network. // RingZeroBits indicates the size of the prefix on the ring 0 (backbone) network.
RingZeroBits = 16 RingZeroBits = 16