Project

General

Profile

Actions
Copy link

Bug #9763

closed
FS JP

Trying to set VLAN Priority causes error

Bug #9763: Trying to set VLAN Priority causes error

Added by Flole Systems almost 7 years ago. Updated almost 7 years ago.

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

100%

Estimated time:
1.00 h
Plus Target Version:
Release Notes:
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/

JP Updated by Jim Pingle almost 7 years ago Actions
Copy link
 #1

  • 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 ()

JP Updated by Jim Pingle almost 7 years ago Actions
Copy link
 #2

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

Applied in changeset commit:93db39ba1b7a72ad936a76aee2fe059a35b8af40.

VG Updated by Viktor Gurov almost 7 years ago Actions
Copy link
 #3

Jim Pingle wrote:

Applied in changeset commit:93db39ba1b7a72ad936a76aee2fe059a35b8af40.

Tested on 2.5.0.a.20191018.2017

Rules with VLAN Prio Set can be changed without problems

Resolved

JP Updated by Jim Pingle almost 7 years ago Actions
Copy link
 #4

  • Status changed from Feedback to Resolved

JP Updated by Jim Pingle almost 7 years ago Actions
Copy link
 #5

  • Target version changed from 2.5.0 to 2.4.5

JP Updated by Jim Pingle almost 7 years ago Actions
Copy link
 #6

  • Status changed from Resolved to Feedback

Needs checked and/or tested again on 2.4.5 snapshots

VG Updated by Viktor Gurov almost 7 years ago Actions
Copy link
 #7

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

JP Updated by Jim Pingle almost 7 years ago Actions
Copy link
 #8

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom