Debugging information is needed to solve complex setup or troubleshooting issues. This information is primarily intended for developers and technical support engineers.

On the 'Diagnostics' page of the web interface, you can check the network connections, view and save the router system log, configure network traffic capture, enable the debug mode, and view a list of active connections with the ports used.

1. Self-test file. Refer to the Saving the self-test file instructions for more information.

To save the self-test file from the 'Diagnostics' page in the 'Self-diagnostics' section, click on 'Download the self-test file'.


The web browser will download the file. If the Save File window appears, specify the location (the folder in which the file will be saved) and press 'Save' or 'OK'.

You can open the self-test.txt system file for viewing in any text editor.

2. System log. Please refer to the System log manual for more information.

3. Network connection test.

In the 'Network connection test' section, you can test the connection to the Internet directly from your Keenetic using the ping and traceroute network utilities. In the 'Host address' field, specify the host's IP address or domain name you want to test and click the 'Start the test' button. Click 'Show settings' to configure more settings.


4. Packet capture.

In the 'Packet Capture' section, you can enable capturing network traffic passing through the selected interface of your Keenetic. You may find more information in the article Network packets capture.

5. For Keenetic models with a built-in DSL modem (Launcher DSL, Carrier DSL, Skipper DSL, Hopper DSL, Hero DSL, Peak DSL), a separate 'DSL' tab is available on the 'Diagnostics' page, which provides connection statistics, parameters for DSL line diagnostics and the ability to report on DSL line quality and causes of disconnection. Detailed information is provided in the DSL connection diagnostics manual.

6. Active connections. A separate 'Active connections' tab displays a list of active connections with the ports used. For example:


7. Debug mode.

In the 'Debug' section, you can enable advanced diagnostics, including detailed logging to the system event log for Internet connections (IPoE, PPPoE, L2TP, PPTP, UsbModem, IPv6) and DHCP server/client.

NOTE: Important! Please do not enable debug mode without a request from a technical support engineer. If you want to give the primary diagnostics to the technical support, save it according to the instructions Saving the self-test system file and send it to the support service.

Follow the steps below if the service engineer has asked you to enable debug mode. Click the 'Restart system in debug mode' button.


NOTE: Important! After enabling or disabling debugging, the current connections will be forcibly re-established.

Thus, if enabling the debug mode is to see the reasons for the interruption of the connection to the ISP, you should wait for the issue to happen after the initially planned reconnection.

After the debug mode is enabled, the message about the date and time of debugging start will appear.


Press the 'Stop debugging' button when the problem occurs or repeats itself.

After that, the self-test.txt file with all necessary debugging information will be automatically downloaded to the computer. The self-test.txt diagnostic file contains diagnostic information and data from the log file and configuration file. The resulting self-test file can be sent to our technical support team for troubleshooting purposes.

NOTE: Important! The settings in the self-test.txt file do not contain passwords, which ensures security when sending it to the support team.

Was this article helpful?

11 out of 14 found this helpful

Have more questions? Submit a request