@extends('admin.firewallplus.layout', ['fwpTab' => 'settings']) @section('fwp_title') Firewall-Plus: Settings @endsection @section('fwp_subtitle') Global limits, SMART defaults & webhooks @endsection @section('fwp') @if (session('success'))
Shown once, before a user activates Firewall-Plus on their first server. Plain text only - no HTML. Leave empty to skip this step entirely.
{{ $message }}
Uncheck to globally disable the AbuseDB tab in the user panel. Users will not see the tab or be able to perform lookups until re-enabled.
Currently {{ number_format($abusedb_saved_count ?? 0) }} saved lookup record(s) stored.
Deletes all saved AbuseIPDB results from storage. Cannot be undone.
Pruned daily by firewall-plus:prune-audit-logs. 90 days is a good default; lower this if your database grows too fast.
firewall-plus:prune-audit-logs
Changing this takes effect on the next node ping cycle.
Default: 60 (once per minute). Example: 120 for a 2-minute cadence.
60
120
These caps are enforced on every save - users cannot exceed them. The node also re-checks them on apply so direct API calls cannot bypass them.
Example: 100. Most servers need fewer than 20.
100
Example: 500. Stored in an ipset - 10,000 entries is still fast.
500
Example: 500. Same ipset performance as whitelist.
Example: 100. Oldest entries must be deleted when full.
These control the allowed range for each field inside a rule. Example: a rate-limit rule's "packets/second" field can be capped to 1–10,000.
50/second
Default: 0.3. Try 0.2 for less sensitive, 0.5 for faster reaction.
0.3
0.2
0.5
Default: 3.0. Lower = more sensitive. Higher = needs bigger spikes.
3.0
Default: 10. First 10 seconds after enable are ignored.
10
Default: 50/second. Example: 100/second for busier servers.
100/second
How long SMART waits after traffic calms down before lowering protection. Think of L1 as a short timeout, L3 as a longer "penalty box" for repeat offenders.
Default: 30s - short relief period.
30s
Default: 120s - escalation after repeated anomalies.
120s
Default: 300s - 5-minute lockdown for persistent attacks.
300s
Grant SMART to individual servers under Servers & SMART.
Firewall-Plus can POST a notification to a URL (e.g. a Discord webhook) whenever something important happens - node goes offline, a limit is hit, emergency mode is toggled. These are infrastructure events. Per-server attack/mitigation alerts are configured by server owners under SMART in the client area.
Supports Discord webhooks, Slack incoming webhooks, or any custom endpoint. Leave blank to disable all panel webhooks.
Uncheck events you don't want to receive notifications for.
{{ $evKey }}
Control how sensitive offline detection is and how many repeat alerts you receive during a long outage.
Default: 2. At 60s interval, that is ~1 minute of failures. Try 3 for more tolerance.
2
3
Default: 3. Set to 1 for a single alert only. Counter resets when the node comes back online.
1