Search results

We have an issue for this feature: https://github.com/soltecsis/fwcloud-api/issues/420 I think that we will implement it soon.

Hi Alasdair, In our last release we added a new feature called Hook Script Rules; you can see a video tutorial about it here. Thanks to this feature you can insert your code in any place of the policy load script generated during the firewall policy compilation process. You can even insert...

The new release will ve available soon, in a few weeks.

This issue has already been solved. It will be fixed in the next release.

We have a GitHub issue about it: https://github.com/soltecsis/fwcloud-ui-src/issues/624 I hope it will be solved in our next release.

Yes, it will work.

Ok, thank you for the suggestions, we will note them in a new issue.

At this moment we have policy compilers for IPTables and NFTables, but we have in mind the option for generate compilers for other packet filtering options.

It is not possible at this moment, but we will evaluate it for a future release. The FWCloud policy management script is installed in the destination firewall into the folder `/etc/fwcloud` and with the name `fwcloud.sh` You can manage the policy using systemd: systemctl stop fwcloud systemctl...

I think that you could do it using a hook script rule. For example, you can generate a hook script rule that inserts code for update git after each policy load. If the script doesn't changes, the git command will do nothing because you don't have any pending changes.

Yes, you are right, it is an interesting feature for avoid blocking the management access from the FWCloud console. I have created a GitHub issue for implement it in the next release. Thank you very much for your feed back.

You can reuse it for nodes in the same cluster, but not reuse rules or group rules for different firewalls. We can evaluate it as a future feature, but I can not grant you that we will implement it because complicates quite a lot the logic of the application.

As you can see in the Docker subsection of the FWCloud installation documentation, you must use HTTPS protocol for access your dockerized FWCloud instance. FWCloud is a security management application, then, the communication with it must be secure too ;-)

Which is the URL that you are using for access the FWCloud Docker instance? Are you using https://localhost:3030? You have to connect using the HTTS protocol.

Fail2Ban and CrowdSec compatibility is independent of the method (ssh or FWCloud-Agent) used to apply the firewall policy into the destination firewall/cluster. Then, if you enable the compatibility flag, it will go for both, ssh and FWCloud-Agent communication.

Hi, Not yet, but we have in our roadmap adding new features to the FWCloud-Agent that will allow a better integration with Fail2Ban and CrowdSec. For example, we have an issue for allow that from the user interface you can query the list of IPs in the CrowdSec blacklist set. Another thing that...

We are very proud to announce the availability of FWCloud-API 1.5.1 and FWCloud-UI 1.4.0, the main packages of the FWCloud project, with lot of new features, performance improvements and bug fixes. This version brings new amazing features like hook scripts rules that will simplify the insertion...

We have just created a new documentation section in the FWCloud website where we explain how to use FWCloud for manage a firewall that has docker images running. Go here for access this document.

FWCloud-Agent is used for manage the firewall in which it is installed. If you want to use it in a Docker container, you will have to generate a new Docker image with FWCloud-Agent installed in it.

Sorry but not at this moment. But if you want to create such documentation we will be pleased to include it in our documentation.