Project

General

Profile

Actions
Copy link

Bug #14146

closed

Small Typo in 'Advanced Outbound firewall rule settings' warning message

Added by Jon Brown over 2 years ago. Updated 19 days ago.

Status:
Closed
Priority:
Very Low
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Affected Version:
2.6.x
Affected Plus Version:
Affected Architecture:
All

Description

When creating an IPv4 outbound permit rule (Firewall --> pfBlockerNG --> Ip --> IPv4) and you leave the Custom Protocol on any you get the following error:

Settings: Protocol setting cannot be set to 'Default' with Advanced Outbound firewall rule settings.

There is a typo where it is saying it cannot be left on 'Default', there is not default protocol. This should read as follows:

Settings: Protocol setting cannot be set to 'Any' with Advanced Outbound firewall rule settings.

I have swapped default for any

Files

Download all files
pfblocker-with-any-error-message.jpg (17 KB) pfblocker-with-any-error-message.jpg Jon Brown, 03/22/2023 07:35 AM
clipboard-202510241453-8lemp.png (15 KB) clipboard-202510241453-8lemp.png aleksei prokofiev, 10/24/2025 11:53 AM
pfblocker-with-any-error-message.jpg (17 KB) pfblocker-with-any-error-message.jpg Jon Brown, 10/24/2025 02:22 PM
Actions
Copy link
 #1

Updated by Marcos M about 2 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Added in pfBlockerNG-devel 3.2.10.

Actions
Copy link
 #2

Updated by aleksei prokofiev 19 days ago

Tested on
25.07.1-RELEASE (amd64)
built on Wed Aug 20 16:17:00 +04 2025
FreeBSD 15.0-CURRENT

pfBlockerNG 3.2.7 and pfBlockerNG-devel 3.2.10
looks good

Actions
Copy link
 #3

Updated by Jim Pingle 19 days ago

  • Status changed from Feedback to Closed
Actions
Copy link
 #4

Updated by Jon Brown 19 days ago

aleksei prokofiev

The image you posted is the same as mine, and the wrong one to be interested in. The issue is in the error message when you try and submitted but it fails validation.

Jim Pingle If you just closed this based on the message from aleksei prokofiev can you recheck this issue has been fixed as his reasons was not valid. It has been over 2 years since I reported this so I am not 100% how to recreate. The issue was/is the The following input errors were detected: that was displayed when I submitted the form, NOT the warning next to the Custom Protocol as this does not appear to of changed since I submitted the issue.

It might of been fixed but, by removing the check on the custom protocol, but if the translation still exists then maybe the problem does.

Thanks

Actions
Copy link

Also available in: Atom PDF