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

…10.11 https://mariadb.com/kb/en/configuring-mariadb-for-remote-client-access/

…eady zones defined there

…uld not be overwritten

…or firewalld

…ndle by services

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 2 times, most recently from 4fdf5ba to 620b0dc Compare July 8, 2024 20:54

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

JeGoi force-pushed the feature/INV-41 branch from 66d88dc to d8743b9 Compare September 9, 2024 18:57

JeGoi added 10 commits October 22, 2024 13:30

Firewalld Add all missing services, move from radius to radiusd

73db81f

Firewalld @radius_int is list of objects

f7de54c

Firewalld Try to fix protocols and helpers

8c40c57

Firewalld Fix protocols and helpers

42e4961

Firewalld Fix policies

9fc19ce

Firewalld fix haproxy admin service

66329ed

Firewalld fix firewalld function

0587a92

Firewalld fix default services

6f9795e

Firewalld fix protocols in default interface config

55cc48d

Firewalld Fix default zone value

da6fc3c

JeGoi added 7 commits October 22, 2024 13:30

Firewalld Update _stop iptables rules

17fefc9

Venom change how to check configurator disabled on in wizard

ed58413

Firewalld move all to direct rules

5a43a37

Firewalld fix cleaning rules

0fd6de4

Firewalld Simplify default zone config

82df8e6

Firewalld Remove unused variables in lib/pf/ipset.pm

b6f1d22

Fix if not a real file, fix if source is empty

fcffd65

JeGoi force-pushed the feature/INV-41 branch from d8743b9 to fcffd65 Compare October 22, 2024 17:31

JeGoi added 20 commits October 22, 2024 15:38

Set iptables legacy

b3e17b0

Remove reference to port and use only socket since upgrade to mariadb…

c0d8c12

…10.11 https://mariadb.com/kb/en/configuring-mariadb-for-remote-client-access/

[Firewalld] Simplify services

1f17404

[Firewalld] Use the default directory for default config of firewalld

c6e8d96

[Firewalld] Clean zones since we are using default directory with alr…

237608c

…eady zones defined there

[Firewalld] Remove example since docker is a default (and perhaps sho…

d2dcca0

…uld not be overwritten

[Firewalld] Add short way to fix files and applied config directory f…

3e3a78e

…or firewalld

[Firewalld] Apply fix dir permission on creation

3817a49

Debianize again

501f089

[Firewalld] Fix file permission function in util

24c18f0

Add missing rule when adding mangle postforwarding

7362967

[Firewalld] Add other missing rules

8b092d8

[Firewalld] Change Forward Netflow position to last

05ca177

[Firewalld] Remove restart service

52c3bc5

[Firewalld] Remove restart service

2e85dfe

[Firewalld] Remove restart service from configurator step4

27a97f2

[Firewalld] Remove reload firewalld configuration, ports should be ha…

ebf1ab9

…ndle by services

[Firewalld] Move masquarade down in order

d4576b1

[Firewalld] Add ipset iptable rulee generate from ipset service too

4802c05

[Firewalld] Give values to filter input position per services

a0e8f09

satkunas modified the milestones: PacketFence-14.1, PacketFence-14.2 Nov 22, 2024

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