Project

General

Profile

Bug #9763

Trying to set VLAN Priority causes error

Added by Flole Systems about 1 month ago. Updated about 22 hours ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Start date:
09/14/2019
Due date:
% Done:

100%

Estimated time:
1.00 h
Affected Version:
All
Affected Architecture:
All

Description

I used to have a rule with VLAN Prio set to VOICE since a few years (so this rule was there during the upgrade to current pfsense aswell). Now I wanted to edit a few parameters on that rule and got "Invalid VLAN Prio Set." even though I didn't change anything related to VLAN Prio (I just switched from Destination Port any to a specific one and from Source Port specific one to any). Once I set VLAN Prio to "Not set" I was able to save it, but now I can no longer set it to anything else as I will get "Invalid VLAN Prio Set." everytime.

Someone else reported the same issue here: https://www.reddit.com/r/PFSENSE/comments/cz7b4i/cannot_utilize_vlan_priority_8021p_matchtag/

Associated revisions

Revision 93db39ba (diff)
Added by Jim Pingle about 1 month ago

Correct input validation for firewall rule VLAN priority/set. Fixes #9763

Revision 9f5ce9d4 (diff)
Added by Jim Pingle about 1 month ago

Correct input validation for firewall rule VLAN priority/set. Fixes #9763

(cherry picked from commit 93db39ba1b7a72ad936a76aee2fe059a35b8af40)

History

#1 Updated by Jim Pingle about 1 month ago

  • Status changed from New to Confirmed
  • Assignee set to Jim Pingle
  • Priority changed from High to Normal
  • Target version set to 2.5.0
  • Affected Version changed from 2.4.4-p3 to All
  • Affected Architecture set to All

#2 Updated by Jim Pingle about 1 month ago

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

#3 Updated by Viktor Gurov 3 days ago

Jim Pingle wrote:

Applied in changeset 93db39ba1b7a72ad936a76aee2fe059a35b8af40.

Tested on 2.5.0.a.20191018.2017

Rules with VLAN Prio Set can be changed without problems

Resolved

#4 Updated by Jim Pingle about 22 hours ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF