firewalld and NetworkManager

[Hans Malissa]

The 'Concepts' page in the firewalld documentation (https://firewalld.org/documentation/concepts.html) describes the interaction between firewalld and NetworkManager as: 'firewalld does not depend on NetworkManager, but the use is recommended. If NetworkManager is not used, there are some limitations...'.
When it comes to compiling and installing both, firewalld and NetworkManager; should NetworkManager or firewalld be built first, and are there some build options (configure options) necessary to make both applications interact?
Greetings,

Hans

[Eric Garver]

On Sat, Jul 20, 2019 at 07:45:00AM +0000, Hans Malissa wrote:
> The 'Concepts' page in the firewalld documentation
> (https://firewalld.org/documentation/concepts.html) describes the
> interaction between firewalld and NetworkManager as: 'firewalld does
> not depend on NetworkManager, but the use is recommended. If
> NetworkManager is not used, there are some limitations...'.

Perhaps this should be redacted. The limitations are negligible as far
as I know. The main one that comes to mind is if NM is used, then zone
may only be "activated" if the interfaces is actually up/enabled. With
standalone firewalld the zones would always be active.
> When it comes to compiling and installing both, firewalld and
> NetworkManager; should NetworkManager or firewalld be built first, and
> are there some build options (configure options) necessary to make
> both applications interact?

It doesn't matter what order you build them. There are no special
options required for firewalld. I don't think there are any special
options for NetworkManager either, but I'm not certain. Just be sure
firewalld starts _before_ NetworkManager. The systemd service files
shipped with each package should handle this appropriately.