Filtering by port, IP, interface, wildcard, etc?

[ghost]

I am looking for an alternative to SimpleWall and TinyWall due to them lacking some features I'd like, but I am not ready to switch (or even try) because WFP is a complex beast on my machine. My VPN comes with 2 WFP drivers - light firewall and traffic diversion. Then I have another WFP driver-based program that intercepts only DNS calls. SimpleWall does not use its own driver and only acts as UI for Base Filtering Engine, which makes it easy to control and configure.

Does Fort Firewall support:

• Filtering by interface (preferably by Adapter NAME and not by Adapter ID that can be dynamic per-session for some VPN programs)?
• Filtering by IP (local and remote rules separated)?
• Filtering by port (local and remote rules separated)?
• Hardware-Enforced Stack Protection (once HVCI is supported)?
• Localhost blocking (per IP or per interface to make compatible with DNSCrypt-Proxy)?
• Executable path wildcards?
• Rule export to Windows Defender Firewall format (for rules without Fort Firewall driver dependencies)?
• Sandboxie support (for non-driver part of Fort Firewall)?

[tnodir]

Filtering by interface (preferably by Adapter NAME and not by Adapter ID that can be dynamic per-session for some VPN programs)?

No. It's in plan, but not soon.

Filtering by IP (local and remote rules separated)?
Filtering by port (local and remote rules separated)?

No. I'm working on this.

Hardware-Enforced Stack Protection (once HVCI is supported)?

Yes, it should be doable.

Localhost blocking (per IP or per interface to make compatible with DNSCrypt-Proxy)?

I don't understand it. You can filter the loopback (127.0.0.1) though.

Executable path wildcards?

Yes.

Rule export to Windows Defender Firewall format (for rules without Fort Firewall driver dependencies)?

No. It's not planned.

Sandboxie support (for non-driver part of Fort Firewall)?

I don't know. Need to research.

[ghost]

Thank you for a thorough response!