Bug #9763
closed
Trying to set VLAN Priority causes error
100%
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/
Updated by Jim Pingle about 5 years 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 All added
- Affected Architecture deleted (
)
Updated by Jim Pingle about 5 years ago
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Applied in changeset 93db39ba1b7a72ad936a76aee2fe059a35b8af40.
Updated by Viktor Gurov about 5 years 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
Updated by Jim Pingle about 5 years ago
- Status changed from Feedback to Resolved
Updated by Jim Pingle about 5 years ago
- Target version changed from 2.5.0 to 2.4.5
Updated by Jim Pingle almost 5 years ago
- Status changed from Resolved to Feedback
Needs checked and/or tested again on 2.4.5 snapshots
Updated by Viktor Gurov almost 5 years ago
Jim Pingle wrote:
Needs checked and/or tested again on 2.4.5 snapshots
tested on 2.4.5.a.20191205.1442_3
ok, Resolved
Updated by Jim Pingle almost 5 years ago
- Status changed from Feedback to Resolved