Thank you for the clarification about ipset. However, the issue I’m facing is that adding an IP to the in_bt_user_accept_ipset does not grant it unrestricted access to the server like the trusted zone in firewalld does.
In firewalld, when I assign an IP to the trusted zone, that IP is allowed to access all open ports on the server without needing to explicitly open those ports in the public zone or elsewhere.
But in the current ipset-based firewall setup, even though the IP is added to in_bt_user_accept_ipset, it cannot access any ports unless those ports are manually opened elsewhere. So the behavior is not equivalent to the trusted zone in firewalld.
My use case is: I want to whitelist certain IPs to have full access to all services (ports) on the server, without needing to manage individual port permissions.
Is there a way to replicate the behavior of the firewalld trusted zone using ipset, or should I disable the new firewall system and go back to using firewalld directly?
