ClearOS Bug Tracker

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

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
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.
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.
Attached Files

- Relationships

-  Notes
(0010601)
NickH (developer)
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.

- Issue History
Date Modified Username Field Change
2010-06-11 09:37 user2 New Issue
2010-06-11 09:38 user2 Status new => confirmed
2019-03-11 06:29 NickH Status confirmed => closed
2019-03-11 06:29 NickH Resolution open => won't fix
2019-03-11 06:30 NickH Assigned To => NickH
2019-03-11 06:30 NickH Status closed => feedback
2019-03-11 06:30 NickH Resolution won't fix => reopened
2019-03-11 06:31 NickH Note Added: 0010601
2019-03-11 06:31 NickH Status feedback => closed
2019-03-11 06:31 NickH Assigned To NickH =>
2019-03-11 06:31 NickH Resolution reopened => won't fix