9bdcbe0447
Major integrations and fixes: - Added BACKBEAT SDK integration for P2P operation timing - Implemented beat-aware status tracking for distributed operations - Added Docker secrets support for secure license management - Resolved KACHING license validation via HTTPS/TLS - Updated docker-compose configuration for clean stack deployment - Disabled rollback policies to prevent deployment failures - Added license credential storage (CHORUS-DEV-MULTI-001) Technical improvements: - BACKBEAT P2P operation tracking with phase management - Enhanced configuration system with file-based secrets - Improved error handling for license validation - Clean separation of KACHING and CHORUS deployment stacks 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
111 lines
5.4 KiB
Markdown
111 lines
5.4 KiB
Markdown
# cidranger
|
|
|
|
Fast IP to CIDR block(s) lookup using trie in Golang, inspired by [IPv4 route lookup linux](https://vincent.bernat.im/en/blog/2017-ipv4-route-lookup-linux). Possible use cases include detecting if a IP address is from published cloud provider CIDR blocks (e.g. 52.95.110.1 is contained in published AWS Route53 CIDR 52.95.110.0/24), IP routing rules, etc.
|
|
|
|
Forked from https://github.com/yl2chen/cidranger due to upstream inactivity.
|
|
|
|
[](https://godoc.org/github.com/libp2p/go-cidranger)
|
|
[](https://travis-ci.org/libp2p/go-cidranger)
|
|
[](https://coveralls.io/github/libp2p/go-cidranger?branch=master)
|
|
[](https://goreportcard.com/report/github.com/libp2p/go-cidranger)
|
|
|
|
This is visualization of a trie storing CIDR blocks `128.0.0.0/2` `192.0.0.0/2` `200.0.0.0/5` without path compression, the 0/1 number on the path indicates the bit value of the IP address at specified bit position, hence the path from root node to a child node represents a CIDR block that contains all IP ranges of its children, and children's children.
|
|
<p align="left"><img src="http://i.imgur.com/vSKTEBb.png" width="600" /></p>
|
|
|
|
Visualization of trie storing same CIDR blocks with path compression, improving both lookup speed and memory footprint.
|
|
<p align="left"><img src="http://i.imgur.com/JtaDlD4.png" width="600" /></p>
|
|
|
|
## Getting Started
|
|
Configure imports.
|
|
```go
|
|
import (
|
|
"net"
|
|
|
|
"github.com/libp2p/go-cidranger"
|
|
)
|
|
```
|
|
Create a new ranger implemented using Path-Compressed prefix trie.
|
|
```go
|
|
ranger := NewPCTrieRanger()
|
|
```
|
|
Inserts CIDR blocks.
|
|
```go
|
|
_, network1, _ := net.ParseCIDR("192.168.1.0/24")
|
|
_, network2, _ := net.ParseCIDR("128.168.1.0/24")
|
|
ranger.Insert(NewBasicRangerEntry(*network1))
|
|
ranger.Insert(NewBasicRangerEntry(*network2))
|
|
```
|
|
To attach any additional value(s) to the entry, simply create custom struct
|
|
storing the desired value(s) that implements the RangerEntry interface:
|
|
```go
|
|
type RangerEntry interface {
|
|
Network() net.IPNet
|
|
}
|
|
```
|
|
The prefix trie can be visualized as:
|
|
```
|
|
0.0.0.0/0 (target_pos:31:has_entry:false)
|
|
| 1--> 128.0.0.0/1 (target_pos:30:has_entry:false)
|
|
| | 0--> 128.168.1.0/24 (target_pos:7:has_entry:true)
|
|
| | 1--> 192.168.1.0/24 (target_pos:7:has_entry:true)
|
|
```
|
|
To test if given IP is contained in constructed ranger,
|
|
```go
|
|
contains, err = ranger.Contains(net.ParseIP("128.168.1.0")) // returns true, nil
|
|
contains, err = ranger.Contains(net.ParseIP("192.168.2.0")) // returns false, nil
|
|
```
|
|
To get all the networks given is contained in,
|
|
```go
|
|
containingNetworks, err = ranger.ContainingNetworks(net.ParseIP("128.168.1.0"))
|
|
```
|
|
To get all networks in ranger,
|
|
```go
|
|
entries, err := ranger.CoveredNetworks(*AllIPv4) // for IPv4
|
|
entries, err := ranger.CoveredNetworks(*AllIPv6) // for IPv6
|
|
```
|
|
|
|
## Benchmark
|
|
Compare hit/miss case for IPv4/IPv6 using PC trie vs brute force implementation, Ranger is initialized with published AWS ip ranges (889 IPv4 CIDR blocks and 360 IPv6)
|
|
```go
|
|
// Ipv4 lookup hit scenario
|
|
BenchmarkPCTrieHitIPv4UsingAWSRanges-4 5000000 353 ns/op
|
|
BenchmarkBruteRangerHitIPv4UsingAWSRanges-4 100000 13719 ns/op
|
|
|
|
// Ipv6 lookup hit scenario, counter-intuitively faster then IPv4 due to less IPv6 CIDR
|
|
// blocks in the AWS dataset, hence the constructed trie has less path splits and depth.
|
|
BenchmarkPCTrieHitIPv6UsingAWSRanges-4 10000000 143 ns/op
|
|
BenchmarkBruteRangerHitIPv6UsingAWSRanges-4 300000 5178 ns/op
|
|
|
|
// Ipv4 lookup miss scenario
|
|
BenchmarkPCTrieMissIPv4UsingAWSRanges-4 20000000 96.5 ns/op
|
|
BenchmarkBruteRangerMissIPv4UsingAWSRanges-4 50000 24781 ns/op
|
|
|
|
// Ipv6 lookup miss scenario
|
|
BenchmarkPCTrieHMissIPv6UsingAWSRanges-4 10000000 115 ns/op
|
|
BenchmarkBruteRangerMissIPv6UsingAWSRanges-4 100000 10824 ns/op
|
|
```
|
|
|
|
## Example of IPv6 trie:
|
|
```
|
|
::/0 (target_pos:127:has_entry:false)
|
|
| 0--> 2400::/14 (target_pos:113:has_entry:false)
|
|
| | 0--> 2400:6400::/22 (target_pos:105:has_entry:false)
|
|
| | | 0--> 2400:6500::/32 (target_pos:95:has_entry:false)
|
|
| | | | 0--> 2400:6500::/39 (target_pos:88:has_entry:false)
|
|
| | | | | 0--> 2400:6500:0:7000::/53 (target_pos:74:has_entry:false)
|
|
| | | | | | 0--> 2400:6500:0:7000::/54 (target_pos:73:has_entry:false)
|
|
| | | | | | | 0--> 2400:6500:0:7000::/55 (target_pos:72:has_entry:false)
|
|
| | | | | | | | 0--> 2400:6500:0:7000::/56 (target_pos:71:has_entry:true)
|
|
| | | | | | | | 1--> 2400:6500:0:7100::/56 (target_pos:71:has_entry:true)
|
|
| | | | | | | 1--> 2400:6500:0:7200::/56 (target_pos:71:has_entry:true)
|
|
| | | | | | 1--> 2400:6500:0:7400::/55 (target_pos:72:has_entry:false)
|
|
| | | | | | | 0--> 2400:6500:0:7400::/56 (target_pos:71:has_entry:true)
|
|
| | | | | | | 1--> 2400:6500:0:7500::/56 (target_pos:71:has_entry:true)
|
|
| | | | | 1--> 2400:6500:100:7000::/54 (target_pos:73:has_entry:false)
|
|
| | | | | | 0--> 2400:6500:100:7100::/56 (target_pos:71:has_entry:true)
|
|
| | | | | | 1--> 2400:6500:100:7200::/56 (target_pos:71:has_entry:true)
|
|
| | | | 1--> 2400:6500:ff00::/64 (target_pos:63:has_entry:true)
|
|
| | | 1--> 2400:6700:ff00::/64 (target_pos:63:has_entry:true)
|
|
| | 1--> 2403:b300:ff00::/64 (target_pos:63:has_entry:true)
|
|
```
|