Open ports aren't necessarily always reported

[Danielle Foré]

It's come to my attention that the settings for both UFW and firewalld can be overridden at a lower level by certain software packages.

If at all possible, we should have some way to check for these open ports and display them in the UI. But at a minimum, we should have some kind of warning information that this is a thing that can occur and that there might be rules somewhere else on the system that are opening other ports.

[Cody Garver (codygarver)]

I experience this, the firewall plug shows as empty but nmap prints the following:

Starting Nmap 7.01 ( https://nmap.org ) at 2017-01-21 23:38 CST
Nmap scan report for localhost (X.X.X.X)
Host is up (0.000062s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
25/tcp open smtp
139/tcp open netbios-ssn
445/tcp open microsoft-ds
631/tcp open ipp
902/tcp open iss-realsecure

[Cody Garver (codygarver)]

I just executed some iptables commands to block everything, now nmap says my ports are closed. So maybe ufw and firewalld can only write to iptables but cannot read the rules it already has?