[pve-devel] [PATCH pve-firewall 1/1] fix #5925: vnet: add parsing logic for log_level_forward
Stefan Hanreich
s.hanreich at proxmox.com
Mon Nov 25 15:30:42 CET 2024
We currently don't parse the log_level_forward option from the vnet
configuration, which leads to the value not being returned from the
API and always showing up as the default nolog value.
Signed-off-by: Stefan Hanreich <s.hanreich at proxmox.com>
---
src/PVE/Firewall.pm | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
index 1db6c51..533f2a2 100644
--- a/src/PVE/Firewall.pm
+++ b/src/PVE/Firewall.pm
@@ -3053,12 +3053,17 @@ sub parse_vnetfw_option {
my ($opt, $value);
+ my $loglevels = "emerg|alert|crit|err|warning|notice|info|debug|nolog";
+
if ($line =~ m/^(enable):\s*(\d+)\s*$/i) {
$opt = lc($1);
$value = int($2);
} elsif ($line =~ m/^(policy_forward):\s*(ACCEPT|DROP)\s*$/i) {
$opt = lc($1);
$value = uc($2);
+ } elsif ($line =~ m/^(log_level_forward):\s*($loglevels)\s*$/i) {
+ $opt = lc($1);
+ $value = lc($2);
} else {
die "can't parse option '$line'\n"
}
--
2.39.5
More information about the pve-devel
mailing list