Key-based peers
WireGuard identifies a peer by its public key. Flirexa generates and stores the matching customer record, assigns an address, renders the configuration, and controls the peer on the live interface.
Available in Community Edition
WireGuard protocol guide
WireGuard provides a deliberately small, modern encrypted tunnel. The operational work is keeping peer identity, addresses, device configurations, and the live server state consistent.
Cross-platform clients
WireGuard is available across Linux, Windows, macOS, Android, iOS, BSD, and other environments. Customers can import a configuration file or scan a QR code where the client supports it.
Small protocol surface
The official project emphasizes simplicity, modern cryptography, and a minimal implementation. That reduces protocol complexity but does not remove the need to secure the server, panel, DNS, or business accounts.
Operational lifecycle
Every device should have its own peer
Reusing one configuration on several devices makes troubleshooting and revocation ambiguous. In Flirexa, a device slot creates an independent client record and key pair.
- allocate the next safe address from the server pool
- generate a dedicated key pair and peer record
- apply the peer to the current WireGuard interface
- deliver a file or QR code through the admin panel or customer portal
- monitor handshake, traffic, expiration, and enabled state
- remove or regenerate one device without changing the others
Device ruleOne peer, key pair, and tunnel address for each device
Stale configuration after endpoint changeWhen the public endpoint or DNS changes, official applications can refresh it; manually downloaded configurations must be downloaded again.
Forwarding or NAT driftA healthy interface does not prove internet reachability. Check kernel forwarding, firewall rules, provider firewalls, return routing, and the correct egress interface.
Common operational failures
Problems rarely come from the cryptography alone
Duplicate AllowedIPs
Two peers using the same tunnel address on one interface can displace each other's route and look like intermittent disconnects. Flirexa serializes allocation and provides an address-integrity audit.
Stale configuration after endpoint change
When the public endpoint or DNS changes, official applications can refresh it; manually downloaded configurations must be downloaded again.
Forwarding or NAT drift
A healthy interface does not prove internet reachability. Check kernel forwarding, firewall rules, provider firewalls, return routing, and the correct egress interface.
Configuration reuse
One peer on several physical devices hides the real device and weakens revocation. Use a separate device slot and configuration for each installation.
Protocol facts on this page are based on the official WireGuard documentation. Flirexa is an independent management platform and does not claim ownership of the WireGuard trademark or project.