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 04:14 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
0000986	ClearOS	app-network - Network Settings	public	2013-02-19 10:34	2013-02-26 20:26
Reporter	user2
Assigned To	user2
Priority	normal	Severity	tweak	Reproducibility	random
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version
Target Version	6.4.0 Beta 2	Fixed in Version
Summary	0000986: Detect default route IP on ppp interfaces even when it does not exist in routing output
Description	On most system using PPPoE, the default route will look like:    default via 10.0.0.1 dev ppp0 But on some systems, the following default route has been reported:    default dev ppp0 The route->get_default_info() reports the default route as 0.0.0.0 which is technically accurate. However, all the API calls are really expecting the real IP (i.e. the remote peer IP). Change the behavior in the API. If there's ever a need to avoid this behavior, a flag can be added to the method.
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0000717) user2 2013-02-19 10:35	Source Code Changelog --------------------------------------------------- - Added extra ppp route detection [fixed tracker 0000986] File Changes --------------------------------------------------- Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=5682 [^] U webconfig/apps/network/trunk/libraries/Routes.php

Notes

Issue History
Date Modified	Username	Field	Change
2013-02-19 10:34	user2	New Issue
2013-02-19 10:34	user2	Assigned To	=> user2
2013-02-19 10:34	user2	Status	new => confirmed
2013-02-19 10:35	user2	Checkin
2013-02-19 10:35	user2	Note Added: 0000717
2013-02-19 10:35	user2	Status	confirmed => resolved
2013-02-19 10:35	user2	Resolution	open => fixed
2013-02-26 20:26	user2	Status	resolved => closed

Issue History