Explore the guide library · Router maintenance
Capture the relevant time window, preserve the original privately and redact the copy you send through an official support channel.
A router log can help explain a connection failure, but it can also contain device identifiers, addresses and service information. Treat an exported log as private network data. Share only what is needed through the manufacturer’s official support process.
Capture the incident precisely
Write down when the failure happened, the router’s timezone, the affected device and the observed symptom. Export relevant logs before a reset or other action that might erase them. GL.iNet’s log guide describes viewing, filtering and exporting several log types on supported firmware.
Keep the original private
Save an unchanged original in a secure location for your own reference. Work on a separate copy for sharing. This preserves diagnostic context if support later asks about a line that was removed.
Review the content deliberately
- Account identifiers and authentication material.
- Public and private addresses.
- Device names and hardware identifiers.
- Visited domains or application details.
- Location, carrier or connection information.
Redact consistently so the relationship between repeated entries remains understandable. For example, replace the same client identifier with the same neutral label throughout the excerpt.
Add an explanation
Include model, hardware revision, firmware, the approximate event time and the steps that reproduce the problem. State what changed recently. A short report with a relevant excerpt is often easier to interpret than an unexplained archive of every available log.
Choose the right destination
Verify the support portal belongs to the vendor before uploading. A public community post is a different audience from a private ticket; never paste a full unreviewed configuration or credential-bearing log into a forum.
Retain the support case reference and remove shared files when the service’s normal process allows and the case no longer requires them. Useful troubleshooting evidence should narrow the problem without unnecessarily exposing the household’s network details.
Sources and editorial notes
Sources checked 8 October 2026. Independent guidance and original illustrations; product comparisons use published specifications rather than hands-on benchmarks. Check the exact model, revision and regional documentation before changing settings.