IPFire Confidence Test Site

I would like there to be an IPFire Confidence Test Site that would test MY IPFire Firewall
and report if there are any security issues with it.
Since supplying TCP address or NIC number is a security risk, I suggest a free test program that the local admin could use to assure that all is well would be a good start.
Thanks for considering…

Hello @gh4light.

You could use NMap or ZenMap (Windows GUI) to do an open ports test. Zenmap - Official cross-platform Nmap Security Scanner GUI

I don’t have much idea of using it. When I use it, I use the default rules. Maybe someone in the forum could put the best parameters to do a test. I know that in Google there are a lot of pages that explain how to use it.

I do it from an external network to the Public IP that I want to attack. Logically, behind that attacked Public IP, there is an IPFire.

It is a good way to start.

You will tell us.

What do you want to be tested?
This is a wide field. IPFire allows many different configurations, each with its own pitfalls. So a test suite for the whole system must know all possible issues. I don’t believe this complexity is manageable.
A test of this sort should give the result “No problems” / “Following problems: …” ( with some completeness). Otherwise one must check logs, config files, … , as without the tool.

Nmap is a good test as roberto mentioned. There are online tests also ( in German for example Network Check at heise.de )

1 Like

Hi all,
Lynis makes also some tests/audits on your system. You can also extend it → How to create custom tests in Lynis - Linux Audit . Otherwise, you can find here → wiki.ipfire.org - System Status via eMail an idea to make may your own check from scratch…



1 Like

I use ionos.com for a $10usd a month package.
Virtual Server Cloud M
. the 2vCores 2GB ram 80GB HDD and a IPv4 Public IP with 400Mbps unlimited transport.

I have in the past installed Kali on the machine and performed my pen-testing from there, currently I have Debian 10 with OpenVPN, PiHole, syslog daemon and metasploit to test with.

As for nmap, it can be a powerful tool but all it really does is check for open ports and report back with the information it was able to gather from services that reply, although there are scripts that do a little more. In metasploit you would use nmap to create a database of host(s) and the open ports and service discovery and then use other tools in the msfconsole to perform intrusion, exfiltration and service/data/network manipulation to generate reports that will allow you to patch and/or reconfigure against those vulnerabilities.

Nmap can:
show you have running services on ports and try to identify them such as SSH or Web server/Apps/SQL/DB etc.
Nmap cant:
tell you if your sshd is vulnerable to a reverse shell
if your httpd/IIS/nginix/tomcat/*SQL has a known CVE and requires a patch or update.

And lastly without knowing how to use these tools to the full extent you may never perform a full suite of pen-testing that would satisfy that little voice “did I miss something?”
So your options IRL are
Educate yourself and continue to do so with tools that will deep dive into the services that you are offering to the public internet
Find a reputable WhiteHat group or organization and pay for their services.
Build trust with someone or a group that just enjoy the “art” of breaking into something.

Be aware that all of the above options have the ability to crash a service(s) and a watchdog or eyes/hands on monitoring during testing is crucial to ensure that a production environment does not become unavailable to those that rely on it’s service.

Thanks to all for the Info…I will be using the info that you provided.