Project

General

Profile

Actions

Feature #12269

closed

Include firewall rules from packages which failed to load in status output

Added by Viktor Gurov 2 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Diagnostics
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
21.09
Release Notes:
Default

Description

discover_pkg_rules() creates the "/tmp/rules.packages.{$pkgname}" file if the package creates unloadable rules.
it would be helpful to add them to status_output for checking

Actions #2

Updated by Jim Pingle 2 months ago

  • Status changed from New to Pull Request Review
  • Assignee set to Viktor Gurov
  • Target version set to 2.6.0
  • Plus Target Version set to 21.09
Actions #3

Updated by Viktor Gurov 2 months ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Viktor Gurov 2 months ago

  • Status changed from Feedback to Resolved

2.6.0.a.20210818.0500 works as expected

Firewall-Generated Package Invalid Ruleset squid:

#There was an error while parsing the package filter rules for /usr/local/pkg/squid.inc.

# Setup Squid proxy redirect
no rdr on vtnet0 proto tcp from any to { asdjasndkasnd, cvncvvcvcvc } port 80
no rdr on $pppoe proto tcp from any to { asdjasndkasnd, cvncvvcvcvc } port 80
rdr pass on vtnet0 inet proto tcp from any to !(vtnet0) port 80 -> 127.0.0.1 port 3128
rdr pass on $pppoe proto tcp from any to !127.0.0.1 port 80 -> 127.0.0.1 port 3128

Actions #5

Updated by Jim Pingle about 2 months ago

  • Tracker changed from Todo to Feature
  • Subject changed from Add incorrectly generated package rules to status_output to Include firewall rules from packages which failed to load in status output

Updating subject for release notes.

Actions

Also available in: Atom PDF