It's not always iptables rules that are being reloaded, could be
nftables. Also the message previously didn't clarify that this is only
reloading the rules for active virtual networks (and not for nwfilter,
for example).
Signed-off-by: Laine Stump <laine@xxxxxxxxxx>
---
src/network/bridge_driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/network/bridge_driver.c b/src/network/bridge_driver.c
index 1b831f9a36..7783473a0f 100644
--- a/src/network/bridge_driver.c
+++ b/src/network/bridge_driver.c
@@ -1735,7 +1735,7 @@ networkReloadFirewallRules(virNetworkDriverState *driver,
bool startup,
bool force)
{
- VIR_INFO("Reloading iptables rules");
+ VIR_INFO("Reloading firewall rules for active virtual networks");
/* Ideally we'd not even register the driver when unprivilegd
* but until we untangle the virt driver that's not viable */
if (!driver->privileged)
--
2.39.2
