We have been able to install FWCloud by means of FWCloud-Installer in a fresh installed and updated Ubuntu 22.04.2 LTS Server. That is something that we usually verify every time a new release is published, but we checked it again just in case.
Are you installing FWCloud in a new server or are...
Hi,
We are trying to reproduce the error in a fresh and updated Ubuntu 22.04 LTS.
I'll inform you with the results of the tests once we finish them.
Thank you for the feedback.
Hi,
We have been testing it in our laboratory environment and its going fine.
Please, may you give us more details about the problem?
Can you include some screenshots about it?
Thanks.
Hi,
At this moment, the Keepalived plugin will install Keepalived software packages in all cluster's nodes and will create a suggested configuration that you can customize by yourself.
In the roadmap for this year we have the addition of a new FWCloud section that will allow Keepalived setup by...
Hi Jeremy,
We have already solved the problem with the target x86_64-unknown-linux-musl in the RPM package process generation.
Thanks to this it is now possible to install FWCloud-Agent in RHEL7, RHEL8 and many other RPM Linux based distributions.
Please, install the new FWCloud-Agent release...
We have just released FWCloud-Agent 1.2.2.
This is a patch releases in which we have improved some issues:
- IPTables package dependency for both `deb` and `rpm` packages.
- GitHub actions `rpm` package generation task for use `--target=x86_64-unknown-linux-musl`. This way the FWCloud-Agent...
We have just released FWCloud-API 1.7.2 and FWCloud-UI 1.6.1.
These are patch releases in which we have solved some bugs:
- Solved problems with the display of the checking for updates dialog.
- Bug in `iptables-save` import procedure when `-p tcp` and `-m tcp` are used at the same time in...
As you can see in the log, the received packet is a TCP RST (https://www.pico.net/kb/what-is-a-tcp-reset-rst/).
Have you checked the communication from this host? Goes it fine?
Who is the owner of the source IP (172.16.1.109) ? Is the FortiGate ?
If you try the communication from any other host connected to the same network, goes it fine ?
Hi Jeremy,
For the RPM package generation we use this YAML code as part of the CI (GitHub Actions) of the FWCloud-Agent repository:
rpm-package:
needs: [build]
runs-on: ubuntu-latest
name: RPM package
steps:
- uses: actions/checkout@v2
- name: Install required...
No risk, only have in mind that you are working with a stateless firewall and maybe you will need to create additional rules.
Your firewall is only for the INPUT chain and you don't need to create rules for the OUTBOUND traffic because the default rule allows it all. Then the change should be...
Then the solution is to replace your "real" firewall with another one managed by means of FWCloud, you can even use a vm based firewall cluster ... I'm just joking ;-)
Maybe your FortiGate perimetral firewall is altering the network traffic in some way that affects the state that FWCloud uses...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.