resolver-debug: alternative for reForis
Because of Turris shield, our approach to DNS debugging with resolver-debug package is not very useful because it has to be run from luci interface
Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
Because of Turris shield, our approach to DNS debugging with resolver-debug package is not very useful because it has to be run from luci interface
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Link issues together to show that they're related. Learn more.
changed milestone to %Turris OS 5.3.0
Resolver debug output can be collected by turris/diagnostics> So we could just handle on/off debugging in reForis.
Yes, it could be collected by turris / diagnostics The historical reason why it was separated to resolver-debug package was, that we didn't want to send verbose DNS log to support because of user privacy violation. If it's no longer a problem it can be done as you suggested.
This should be in turris/reforis/reforis> project, shouldn't it?
changed title from resolver-debug: create alternative for reForis to resolver-debug: alternative for reForis
moved to turris/reforis/reforis#265
removed Backlog label