For whom: Panel Administrator / SRE. Required rights: Administrator session; node requires an agent with firewall support.
Don’t confuse Egress Guard with “external transit egress blocks” – this is another feature: VLESS hops in the Flow column, see Routing Flow.
Principle “Save ⁇ applied”
The changes first save the desired policy, and the status of its application by node is displayed separately in the Apply tab.Category catalogue
The directory is fixed - there is no free list of ports in the standard interface, and it is consciously:- Actions:
drop,reject,detect(detection does not put a rule in the firewall - only powers the detectors). - DNS (53) and NTP (123) are never consciously blocked by, instead of being blocked by an anomalous fan-out detector.
- Port redefinition is only available in extended mode; policies with unknown categories, activities, or ports are rejected.
How reconciliation works
- The policy is stored with a single entry with the version (each save raises the version) and the
auto_reapplyflag. - About every 5 minutes, the panel bypasses all the nodes: if the desired hash has changed or the rules have not yet been applied, it sends an application; otherwise it performs a cheap state reading that catches the drift that occurred outside the panel (manual rule reset, node reboot).
- Auto repair drift is performed only when switched on
auto_reapply- and never in the same aisle that he just applied the rules (cycle protection), when the flag is turned off, the drift is simply fixed and left to the operator’s decision. - A node whose agent does not support firewall operations is shown as
unsupported, not “applied.” - Node statuses:
pending,applied,drift,failed,unsupported,unknownare sorted from worst to best in the interface. Policy changes and reconciliation actions are written in the audit log.
Setting up
1
See the directory and current policy
Open Security by Egress Guard.
2
Keep the policy.
Enable the desired categories and click Save policy.
3
Apply now (if desired)
Go to the tab Application and click Convert now.
Verification
- After changing the policy, wait for the scheduled reconciliation or click Contact nowZ.
The protection is valid on the node if its status -
appliedThat is, the hash of the rules in the nucleus of the node coincided with the desired.Rollback
- Unlock the lock: Turn off the category or transfer it to
detect, save the policy and click Contact now. - Auto repair drift can be turned off with the
auto_reapplyflag - the panel will cease to arbitrarily return the rules and will only report drift.
Limitations and risks
detectcategories don’t protect traffic – they only observe.- There is a window (up to one reconciliation cycle) between maintaining the policy and applying it.
- On nodes without firewall support, the agent does not have protection - the status of
unsupportedrequires updating or reconfiguring the agent.
Node hangs in drift
Node hangs in drift
Open the tab Application and click Confirm Now. If auto repair is enabled, the panel will reapply the desired state.
Node shows off unsupported
Node shows off unsupported
The agent on the node has no firewall capability. Check the agent’s version and capabilities on the node page.
Maintained policy, and status is still pending
Maintained policy, and status is still pending
This is normal immediately after saving. Wait for the reconciliation cycle or press Contact now.
