Port range in classifier policy does not work

Bug #1482718 reported by venkat akkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy UI
Confirmed
Medium
ank

Bug Description

Able to configure port range in classifier policy for all protocols but observed that ports configured are not working.
Basically the port is not getting configured in services.

Changed in group-based-policy-ui:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → ank (ank.b)
milestone: none → next
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.