Look up unfamiliar terms here while reading the docs. For concept explanations, see Core concepts.
| Term | Meaning |
|---|
| FF1 Master | Control-plane main service: console, Admin API, config-delivery scheduling |
| FF1 Core | Data-plane forwarding engine installed on each node; performs forwarding and reports status |
| Node | A VPS / physical machine running FF1 Core—your relay machine |
In the license quota, node count (servers_cont) = number of registered nodes; forward rule count (forward_count) = number of created forwarding rules.
| Term | Description |
|---|
| Forward rule | An “entry port → target address:port” mapping; supports same-position, same-number pass-through of port ranges/lists |
| Same-position pass-through | Entry and exit ports map one-to-one (e.g. 50-60,80,90-200), no per-port mapping needed |
| Tunnel / nesting | A forwarding chain of multiple nodes (A→B→C), linked level by level via upstream_tunnel_id |
| Config delivery queue | The delivery task queue; held when a node is offline, auto-re-pushed on recovery. A chain change re-pushes to every node on the chain |
| Rate limiting | Kernel-level traffic shaping based on tc HTB, stable across low and high speed tiers |
| Real-IP pass-through | Optional PROXY protocol that passes the client’s real IP to the upstream |
| Term | Description |
|---|
| User | A console operator account, assigned as needed for multi-operator operations |
| API Token | A token for scripted calls to the Master REST API, authorized by scope |
| Scope | Token permission, in the form nodes:read, rules:write, tunnels:write, audit:read |
| Term | Description |
|---|
| License | An authorization purchased from the website, constraining node count, forward rule count, and validity period |
| Audit log | A traceable record of key write operations in the console and Admin API |
| Telegram notifications | Push alerts and key events to a Telegram Bot |
Operational details are governed by each topic page; the glossary is only a quick reference.
