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-21 23:45 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
0001475	ClearOS	app-port-forwarding - Port Forwarding	public	2013-12-18 08:03	2014-01-22 06:20
Reporter	bchambers
Assigned To	bchambers
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version	6.5.0
Target Version	6.5.0 Updates	Fixed in Version	6.5.0 Updates
Summary	0001475: Firewall will panic if port ranges are entered in the port to port forward form (2nd form)
Description	The 2nd form for adding port forward rules allows port ranges using : delimiter. This form should not allow port ranges and is designed only for single port mappings (eg. port 2200 --> 22). Port forward ranges entered using the single port form will result in firewall panicking.
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0001108) bchambers (administrator) 2013-12-18 09:56	Source Code Changelog --------------------------------------------------- Prevents port ranges from being entered (force port range form) [fixed tracker 0001475] File Changes --------------------------------------------------- Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=6745 [^] U webconfig/apps/port_forwarding/trunk/controllers/port_forwarding.php U webconfig/apps/port_forwarding/trunk/deploy/info.php U webconfig/apps/port_forwarding/trunk/libraries/Port_Forwarding.php U webconfig/apps/port_forwarding/trunk/packaging/app-port-forwarding.spec U webconfig/apps/port_forwarding/trunk/views/summary.php

Notes

Issue History
Date Modified	Username	Field	Change
2013-12-18 08:03	bchambers	New Issue
2013-12-18 08:03	bchambers	Status	new => assigned
2013-12-18 08:03	bchambers	Assigned To	=> bchambers
2013-12-18 09:56	bchambers	Checkin
2013-12-18 09:56	bchambers	Note Added: 0001108
2013-12-18 09:56	bchambers	Status	assigned => resolved
2013-12-18 09:56	bchambers	Resolution	open => fixed
2014-01-22 06:20	bchambers	Status	resolved => closed
2014-01-22 06:20	bchambers	Fixed in Version	=> 6.5.0 Updates

Issue History