Write your rules in the console
Interfaces, inbound, outbound and forwarded rules, aliases, NAT, import from OPNsense or pfSense: all in a draft you reread before loading.
Two optional modules to write the firewall rules of the ToutWAF machine and prepare VPN access. They are off by default and not yet proven in production: this page says what exists, what does not, and how to try them safely.
Where to find it in the console : Administration menu: Settings, Modules tab; the Firewall and VPN sections appear in the menu only when the module is on.
These two modules are experimental. We prefer to say so before describing anything.
Interfaces, inbound, outbound and forwarded rules, aliases, NAT, import from OPNsense or pfSense: all in a draft you reread before loading.
A guard simulates the flows that must never be cut, and every application is put on trial with an automatic return if you do not confirm.
Keys, certificates and ready-to-use files for WireGuard, OpenVPN and IPsec/IKEv2, kept encrypted with the master key.
One switch per module, reserved to platform administrators, recorded in the audit log.
Nothing is loaded until you apply, and nothing is kept until you confirm.
Everything is edited in a draft. Saving it changes nothing on the machine.
« Show changes » compares with the rules in force and simulates the flows that must never be cut: console (443 and 9443), SSH (22), agent port (9444), ToutWAF and its peers. A flow cut everywhere is refused; a flow cut in part is a warning.
Applying loads the rules in their own nftables table, without touching the other tables, including those of firewalld. Without your confirmation within 60 seconds, the previous rules come back by themselves.
Settings > Modules, or the optional « Modules » step of the first-launch assistant. Only a platform administrator can change them.
In the style of OPNsense, with nftables as the engine, on a Linux host.
This is not the firewall that opens the ports ToutWAF needs: that card, in Settings, always exists. This module is for your own rules.
The configuration of servers, clients and outgoing connections, generated and kept.
The page says it too: « Only the configuration is generated and stored. Nothing is started and no port is opened on this machine. »
We prefer to say it plainly.
You import an export into the draft and read the plan without applying anything.
You generate a WireGuard server and each person's files, then install the server side yourself.
You apply a visible change, confirm or let the automatic return act, then decide.
In this version neither module is tied to a licence; that may change.
Every function in this list carries the note « not yet proven in production ». The data plane, for its part, never consults the licence.
Precios Read the documentation
Instálelo en su propio servidor, o escríbanos para hablar de licencias.