Feature/inv 41 Firewalld in PF #8055

JeGoi · 2024-04-02T19:36:36Z

Description

Move from iptables to firewalld
Make things more dynamic to update the firewall rules.

Impacts

Get out of iptables

Code / PR Dependencies

feature/INV-41 on figerbank-collector

Delete branch after merge

YES

Checklist

Document the feature
Update venom tests

NEWS file entries

New Features

Move from iptables to firewalld

conf/firewalld/firewalld_services.conf.defaults

lib/pf/Firewalld/icmptypes.pm

lib/pf/services/manager/firewalld.pm

lib/pfconfig/namespaces/config/Firewalld_Helpers.pm

lib/pfconfig/namespaces/config/Firewalld_Icmptypes.pm

lib/pfconfig/namespaces/resource/all_firewalld.pm

conf/documentation.conf

conf/firewalld/firewalld.conf.example

conf/firewalld/firewalld_services.conf.defaults

fdurand · 2024-06-14T17:56:50Z

conf/firewalld/firewalld_services.conf.defaults

+port=1822
+type=tcp
+[radius_auth_clu_port3]
+port=2093


it's the radsec one

conf/firewalld/firewalld_services.conf.defaults

conf/pf.conf.defaults

fdurand · 2024-06-14T19:41:09Z

conf/systemd/packetfence-httpd.admin_dispatcher.service

 Before=packetfence-haproxy-admin.service
-Before=packetfence-docker-iptables.service
-Requires=packetfence-docker-iptables.service
-PartOf=packetfence-docker-iptables.service


Why there is no call to generate the firewalld config ?

Because it is starting at the installation https://github.com/inverse-inc/packetfence/blob/feature/INV-41/debian/packetfence.postinst#L228, and at this point pfconfig is empty.
There is no config done.
In current Devel, iptables is started at this point at the same point docker-iptables service is a fake one. https://github.com/inverse-inc/packetfence/blob/devel/conf/systemd/packetfence-docker-iptables.service#L9

In fact that iptables service dependency at boot is using the fact that the service iptables during pf installation will fail.
Thanks to the failure, at the exiit of iptables, new rules are defined.

-- Journal begins at Wed 2024-07-10 11:19:44 UTC, ends at Wed 2024-07-10 11:44:36 UTC. -- [13/1674] Jul 10 11:29:53 172-234-151-109 systemd[1]: Started PacketFence Iptables configuration. Jul 10 11:29:55 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:29:56 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:29:57 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:29:58 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:29:59 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:00 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:01 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:02 172-234-151-109 systemd[1]: Stopping PacketFence Iptables configuration... Jul 10 11:30:02 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:03 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:04 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:05 172-234-151-109 sudo[31331]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -F Jul 10 11:30:05 172-234-151-109 sudo[31331]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31331]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31334]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -X Jul 10 11:30:05 172-234-151-109 sudo[31334]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31334]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31337]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -F Jul 10 11:30:05 172-234-151-109 sudo[31337]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31337]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31340]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -X Jul 10 11:30:05 172-234-151-109 sudo[31340]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31340]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31343]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t mangle -F Jul 10 11:30:05 172-234-151-109 sudo[31343]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31343]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31346]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t mangle -X Jul 10 11:30:05 172-234-151-109 sudo[31346]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31346]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31349]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -P INPUT ACCEPT Jul 10 11:30:05 172-234-151-109 sudo[31349]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31349]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31352]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -P FORWARD ACCEPT Jul 10 11:30:05 172-234-151-109 sudo[31352]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31352]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31355]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -P OUTPUT ACCEPT Jul 10 11:30:05 172-234-151-109 sudo[31355]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31355]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31358]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -N DOCKER Jul 10 11:30:05 172-234-151-109 sudo[31358]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31358]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31361]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER Jul 10 11:30:05 172-234-151-109 sudo[31361]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31361]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31364]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER Jul 10 11:30:05 172-234-151-109 sudo[31364]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31364]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31367]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -A POSTROUTING -s 100.64.0.0/10 ! -o docker0 -j MASQUERADE Jul 10 11:30:05 172-234-151-109 sudo[31367]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31367]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31370]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -A DOCKER -i docker0 -j RETURN Jul 10 11:30:05 172-234-151-109 sudo[31370]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31370]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 systemd[1]: packetfence-iptables.service: Succeeded. Jul 10 11:30:05 172-234-151-109 systemd[1]: Stopped PacketFence Iptables configuration. Jul 10 11:30:05 172-234-151-109 systemd[1]: packetfence-iptables.service: Consumed 5.222s CPU time.

So it is tricky, because we are using iptables in order to have the rules defined when it is failing.

In fact that iptables service dependency at instlation is using the fact that the service iptables during pf installation will fail. The db is not yet defined and there is no connexion.
Thanks to the failure, at the exiit of iptables, new rules are defined.

-- Journal begins at Wed 2024-07-10 11:19:44 UTC, ends at Wed 2024-07-10 11:44:36 UTC. -- [13/1674] Jul 10 11:29:53 172-234-151-109 systemd[1]: Started PacketFence Iptables configuration. Jul 10 11:29:55 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:29:56 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:29:57 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:29:58 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:29:59 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:00 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:01 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:02 172-234-151-109 systemd[1]: Stopping PacketFence Iptables configuration... Jul 10 11:30:02 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:03 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:04 172-234-151-109 packetfence[30662]: -e(30662) ERROR: unable to connect to database: Access denied for user 'pf'@'localhost' (pf::db::db_connect) Jul 10 11:30:05 172-234-151-109 sudo[31331]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -F Jul 10 11:30:05 172-234-151-109 sudo[31331]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31331]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31334]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -X Jul 10 11:30:05 172-234-151-109 sudo[31334]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31334]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31337]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -F Jul 10 11:30:05 172-234-151-109 sudo[31337]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31337]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31340]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -X Jul 10 11:30:05 172-234-151-109 sudo[31340]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31340]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31343]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t mangle -F Jul 10 11:30:05 172-234-151-109 sudo[31343]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31343]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31346]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t mangle -X Jul 10 11:30:05 172-234-151-109 sudo[31346]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31346]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31349]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -P INPUT ACCEPT Jul 10 11:30:05 172-234-151-109 sudo[31349]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31349]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31352]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -P FORWARD ACCEPT Jul 10 11:30:05 172-234-151-109 sudo[31352]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31352]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31355]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -P OUTPUT ACCEPT Jul 10 11:30:05 172-234-151-109 sudo[31355]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31355]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31358]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -N DOCKER Jul 10 11:30:05 172-234-151-109 sudo[31358]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31358]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31361]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER Jul 10 11:30:05 172-234-151-109 sudo[31361]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31361]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31364]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER Jul 10 11:30:05 172-234-151-109 sudo[31364]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31364]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31367]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -A POSTROUTING -s 100.64.0.0/10 ! -o docker0 -j MASQUERADE Jul 10 11:30:05 172-234-151-109 sudo[31367]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31367]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 sudo[31370]: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/iptables -t nat -A DOCKER -i docker0 -j RETURN Jul 10 11:30:05 172-234-151-109 sudo[31370]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jul 10 11:30:05 172-234-151-109 sudo[31370]: pam_unix(sudo:session): session closed for user root Jul 10 11:30:05 172-234-151-109 systemd[1]: packetfence-iptables.service: Succeeded. Jul 10 11:30:05 172-234-151-109 systemd[1]: Stopped PacketFence Iptables configuration. Jul 10 11:30:05 172-234-151-109 systemd[1]: packetfence-iptables.service: Consumed 5.222s CPU time.

So it is tricky, because we are using iptables in order to have the rules defined when it is failing.

conf/systemd/packetfence-snmptrapd.service

lib/pf/firewalld.pm

JeGoi · 2024-06-26T15:15:55Z

Needs dedicated log file

JeGoi · 2024-07-08T13:16:07Z

These services have a systemd service related to firewalld but no rules related:

# conf/systemd/packetfence-httpd.dispatcher.service # DONE

conf/systemd/[email protected]
conf/systemd/packetfence-ntlm-auth-api.service
conf/systemd/packetfence-pfconnector-client.service
conf/systemd/packetfence-pfdetect.service
conf/systemd/packetfence-pfdhcplistener.service
conf/systemd/packetfence-pffilter.service
conf/systemd/packetfence-pfldapexplorer.service
conf/systemd/packetfence-pfpki.service
conf/systemd/packetfence-pfqueue-perl.service
conf/systemd/packetfence-pfsetacls.service
conf/systemd/packetfence-pfsso.service
conf/systemd/packetfence-pfstats.service
conf/systemd/packetfence-radsniff.service
conf/systemd/packetfence-redis_ntlm_cache.service

…ystemd services

…onfig hard

… yet

…rewalld to not start when pf is installed

…ig file is not there

…nt interface is defined

… rules

…stop without failing

…stretch and bullseye" This reverts commit c7600c6.

…rewalld service is in other service

JeGoi added this to the PacketFence-13.2 milestone Apr 2, 2024

JeGoi requested a review from fdurand April 2, 2024 19:36

fdurand reviewed Apr 3, 2024

View reviewed changes

JeGoi force-pushed the feature/INV-41 branch from a7d4c8d to 991048e Compare April 16, 2024 17:01

satkunas modified the milestones: PacketFence-13.2, PacketFence-14.0 Apr 18, 2024

JeGoi force-pushed the feature/INV-41 branch from b539c4b to 77e3f89 Compare May 17, 2024 16:48

JeGoi force-pushed the feature/INV-41 branch 2 times, most recently from c7e9808 to 64290f6 Compare June 5, 2024 13:50

fdurand reviewed Jun 14, 2024

View reviewed changes

JeGoi force-pushed the feature/INV-41 branch from 22e7c31 to b0d7557 Compare June 19, 2024 18:56

JeGoi force-pushed the feature/INV-41 branch 2 times, most recently from 9e76f84 to aeb44f5 Compare June 27, 2024 16:17

JeGoi force-pushed the feature/INV-41 branch from 5a422c5 to 4fdf5ba Compare July 8, 2024 20:25

JeGoi and others added 14 commits July 8, 2024 16:52

Firewalld Add function per services

da2b47d

Firewalld fix remaning chains

7d278e2

Firewalld restore la moo

d3532c6

Firewalld Fix add service

daf3945

Added firewalld to pf.conf

91967d2

Add new function for getting current service state

0e843e6

Firewalld Split radius and add cluster, add several fd services for s…

98978db

…ystemd services

Firewalld Add radius load balancer and fix radius cli cluster

94d41dd

Firewalld Move 7070 from radius load balancer to httpd_aaa

b7b6155

Firewalld Add api frontend

a505d99

Firewalld Add function per service, fix restart firewalld service

946f356

Firewalld Fix compilation issues and zones config

14a5a23

Firewalld Add firewalld config for services api frontend

b418399

Firewalld Add firewalld config for systemd packetfence-firewalld

aadfbc2

JeGoi added 2 commits July 8, 2024 16:52

Firewalld Add http and https to vlan enforcement interfaces

d4ab9d4

Firewalld Change from restart firewalld service to reload firewalld c…

620b0dc

…onfig hard

JeGoi force-pushed the feature/INV-41 branch from 4fdf5ba to 620b0dc Compare July 8, 2024 20:54

JeGoi added 22 commits July 8, 2024 17:14

Firewalld Add t/venom reload config firewalld in lib as executor

a6aa0b6

Firewalld WAKE up gitlab

34605ac

Firewalld bring back the orginal docker minimal rules

8745a72

Firewalld Add firewalld in general for logs

e670cd1

Firewalld Fix dns issue, with not remove chain

2ce94a7

Firewalld add dns, dhcp http and https on managment interface too

d3d0c20

Firewalld add haproxy-admin port on service for management int

a6c3b72

FIrewalld Remove firewalld config relaod since service is not started…

0d21774

… yet

Firewalld Fix default minimal rules with exit of iptables or firewalld

fa773c3

Firewalld Restore firewalld dependence for api-frontend and expect fi…

a2da4a3

…rewalld to not start when pf is installed

Firewalld Allow firewalld to stop without failing when firewalld conf…

b38153d

…ig file is not there

Firewalld Allow firewalld to start ExecStartPost only if the manageme…

e3b2328

…nt interface is defined

Firewalld Avoid cleaning iptables before trying to add docker mininal…

4edc755

… rules

Firewalld Add back firewalld in httpd.admin-dispatcher with comments

8b85d6a

Firewalld Bring back the configurator as it was, since firewalld can …

45aacdb

…stop without failing

Revert "Firewalld Set mysql root password empty, remove reference to …

5e60ec0

…stretch and bullseye" This reverts commit c7600c6.

Firewalld Restore docker minimal rules to a complete minimum since fi…

fc76972

…rewalld service is in other service

Firewalld Restore debian post install

b4029c0

Firewalld Restore redhat post install

fe8dc46

Forewalld debianize patch number 42 as the answer

b83ba07

Firewalld Update _stop iptables rules

3c423a4

Venom change how to check configurator disabled on in wizard

e18685a

satkunas modified the milestones: PacketFence-14.0, PacketFence-14.1 Jul 11, 2024

JeGoi added 3 commits July 11, 2024 21:35

Firewalld move all to direct rules

1336dec

Firewalld fix cleaning rules

f3db36f

Firewalld Simplify default zone config

66d88dc

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Feature/inv 41 Firewalld in PF #8055

Feature/inv 41 Firewalld in PF #8055

JeGoi commented Apr 2, 2024 •

edited

Loading

fdurand Jun 14, 2024

fdurand Jun 14, 2024

JeGoi Jun 14, 2024 •

edited

Loading

JeGoi Jul 10, 2024

JeGoi Jul 10, 2024 •

edited

Loading

JeGoi commented Jun 26, 2024

JeGoi commented Jul 8, 2024 •

edited

Loading

Feature/inv 41 Firewalld in PF #8055

Are you sure you want to change the base?

Feature/inv 41 Firewalld in PF #8055

Conversation

JeGoi commented Apr 2, 2024 • edited Loading

Description

Impacts

Code / PR Dependencies

Delete branch after merge

Checklist

NEWS file entries

New Features

fdurand Jun 14, 2024

Choose a reason for hiding this comment

fdurand Jun 14, 2024

Choose a reason for hiding this comment

JeGoi Jun 14, 2024 • edited Loading

Choose a reason for hiding this comment

JeGoi Jul 10, 2024

Choose a reason for hiding this comment

JeGoi Jul 10, 2024 • edited Loading

Choose a reason for hiding this comment

JeGoi commented Jun 26, 2024

JeGoi commented Jul 8, 2024 • edited Loading

JeGoi commented Apr 2, 2024 •

edited

Loading

JeGoi Jun 14, 2024 •

edited

Loading

JeGoi Jul 10, 2024 •

edited

Loading

JeGoi commented Jul 8, 2024 •

edited

Loading