-
Notifications
You must be signed in to change notification settings - Fork 0
quick start
You will learn how to build update-ipsets from source, run it locally, and try its main features. The daemon starts quickly; the first full catalog download continues in the background.
- Go 1.26 or later
- Git
- pnpm
- A terminal
Clone the repository and build the binary:
git clone https://github.com/firehol/update-ipsets.git
cd update-ipsets
make buildThis produces the update-ipsets binary in the project root.
The build also installs and builds the embedded web UI with pnpm.
Start the daemon with the bundled catalog on a local port:
./update-ipsets daemon \
--config configs/firehol \
--listen :18888 \
--enable-all \
--admin-auth-mode=disabled \
--allow-unauthenticated-adminFlags explained:
-
--config configs/firehol— use the bundled feed catalog -
--listen :18888— serve on port 18888 -
--enable-all— make the bundled catalog active without creating enable marker files first -
--admin-auth-mode=disabled --allow-unauthenticated-admin— open admin for local testing (do not use in production)
- Public site: http://localhost:18888/
- Admin UI: http://localhost:18888/admin
The public site shows the feed explorer, IP search, and comparisons. The admin UI shows download/processing queues and feed status. On a fresh checkout, wait for the relevant feeds to finish downloading and processing before expecting query results.
Look up which feeds contain an IP address:
./update-ipsets query 1.2.3.4Count unique IPs across CIDR ranges using the iprange subcommand:
printf "1.0.0.0/8\n2.0.0.0/8\n" | ./update-ipsets iprange --count-uniqueCompose sets and test membership:
./update-ipsets query --set "firehol_level1 + firehol_level2" 1.2.3.4- Installation — production deployment with systemd, TLS, and memory planning
- Configuration Concepts — how the YAML catalog works
- Feed Families — the six feed families and when to use each
- Daemon Command Reference
- Environment Variables
- Configuration Reload
- Listener Topologies
- Admin Authentication
- Feed Families
- Source Feeds
- Processor Reference
- Static Feeds
- Merge Feeds
- Artifact Parents
- History Derivatives
- Provider Databases
- Use Roles
- Critical Infrastructure Reference Feeds
- Legal Fields
- Feed Visibility & Lifecycle
- YAML Field Reference
- Pipeline Overview
- Download Lifecycle
- Processing Lifecycle
- Feed Status Reference
- Health Classes
- What Triggers Reprocessing
- Accessing the Admin
- Runtime Status
- Feed Inventory
- Artifact Inventory
- Live Queues
- Background Work
- Schedule State
- Operator Actions
- Enable & Disable