ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000107ClearOSapp-syswatch - System Watchpublic2010-06-11 09:372019-03-11 06:31
Reporteruser2 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionwon't fix 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000107: Syswatch does not detect the 172.16.0.0/12 network, effectively disabling dynamic DNS updates
DescriptionThe syswatch software does not detect the 172.16.0.0/12 network. If a user happens to have a public IP in the 172.17.x.x to 172.255.x.x address space, the dynamic DNS update will fail.
Steps To Reproduce
Additional InformationA temporary workaround for users in this predicament is to add the following to /etc/syswatch

use_get_ip=enabled

And then restart syswatch:

service syswatch restart
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-06-11 09:37user2New Issue
2010-06-11 09:38user2Statusnew => confirmed
2019-03-11 06:29NickHStatusconfirmed => closed
2019-03-11 06:29NickHResolutionopen => won't fix
2019-03-11 06:30NickHAssigned To => NickH
2019-03-11 06:30NickHStatusclosed => feedback
2019-03-11 06:30NickHResolutionwon't fix => reopened
2019-03-11 06:31NickHNote Added: 0010601
2019-03-11 06:31NickHStatusfeedback => closed
2019-03-11 06:31NickHAssigned ToNickH =>
2019-03-11 06:31NickHResolutionreopened => won't fix

Notes
(0010601)
NickH   
2019-03-11 06:31   
172.16/12 is a non-routable private addrese space. This bug may be coming from an AWS user since amazon used 172.16/12 for their networks. But they always use public for their elastic IPs. This is a percieved problem only and not a real one.