SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: Connection refused' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-12-22 05:04 MST

Project: All Projects ClearCenter ClearOS

Main | My View | View Issues | Change Log | Roadmap | Repositories

View Issue Details [ Jump to Notes ]				[ Issue History ] [ Print ]
ID	Project	Category	View Status	Date Submitted	Last Update
0020341	ClearOS	app-qos - QoS	public	2018-06-11 03:22	2019-02-23 13:09
Reporter	NickH
Assigned To	dloper
Priority	normal	Severity	tweak	Reproducibility	always
Status	closed	Resolution	suspended
Platform		OS		OS Version
Product Version	7.4.0
Target Version	7.6.0 Updates	Fixed in Version
Summary	0020341: Change "Source/Destination Address" text to "Source/Destination Address/Subnet"
Description	In app-qos, the Source Address and Destination Address fields can take whole subnets in both CIDR and /255.255.255.0 type of notation. As a use case, this is good for dedicated VoIP LANs/VLANs. The Webconfig only says Source Address and Destination Address giving no indication that subnets can be used. Can the "Source Address" field test be changed to "Source Address/Subnet" and "Destination Address" be changed to "Destination Address/Subnet"? Also applies to 7.5 Beta
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0007601) user2 2018-06-25 14:40	Let's use the word "Target" instead of "Address/Subnet". We need to double check to make sure subnets are allowed in the new QoS engine.
(0009241) dloper (administrator) 2019-02-23 13:09	Migrated to: https://gitlab.com/clearos/clearfoundation/app-qos/issues/1 [^]

Notes

Issue History
Date Modified	Username	Field	Change
2018-06-11 03:22	NickH	New Issue
2018-06-11 07:11	user2	Status	new => acknowledged
2018-06-11 07:11	user2	Target Version	=> 7.5.0 Updates
2018-06-25 14:40	user2	Note Added: 0007601
2018-10-30 18:18	user2	Target Version	7.5.0 Updates => 7.6.0
2018-11-05 09:23	user2	Target Version	7.6.0 => 7.6.0 Updates
2019-02-23 13:09	dloper	Note Added: 0009241
2019-02-23 13:09	dloper	Status	acknowledged => closed
2019-02-23 13:09	dloper	Assigned To	=> dloper
2019-02-23 13:09	dloper	Resolution	open => suspended

Issue History