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

rings: fix NodeZeroMax/NodeMax to not accept .255 

Signed-off-by: Alejandro Mery <amery@jpi.io>
pull/50/head
Alejandro Mery 7 months ago
parent
ff8f2c6ea1
commit
6d89e0ea3c
1 changed files with 2 additions and 2 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 4
      pkg/rings/rings.go

4
pkg/rings/rings.go
Unescape 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

Write Preview
Loading…
Cancel
Save