Explore the guide library · Security and privacy
Check both protocol paths when validating guest access, administration and filtering after a router change.
A router replacement can change which internet protocols your clients use. If IPv6 becomes available, verify the access policy on that path as well as IPv4. Do not assume an old forwarding or filtering rule automatically describes every new connection.
Write the intended policy plainly
Examples include visitors being unable to reach private storage, router administration being available only to authorized local devices, or a particular application requiring an approved tunnel. State the desired behavior before looking for a matching menu.
Check feature support
Read the firmware documentation for the exact feature and protocol. GL.iNet’s IPv6 guide currently warns of limitations with some functions. Such notes matter more than assuming a feature works across all traffic because its switch is enabled.
Test using your own devices
- Identify whether the test client has working IPv4 and IPv6 connectivity.
- Check the intended allowed resource through the supported route.
- Check that a prohibited local resource remains unavailable.
- Review the administration interface’s permitted networks.
- Repeat after a normal restart or lease renewal.
Use only devices and networks you are authorized to test. Keep full addresses and diagnostic output private when sharing results.
Avoid incomplete fixes
Do not open broad inbound access to resolve an unexplained application problem. Similarly, turning off a protocol may hide a compatibility issue without establishing a maintainable configuration. Choose a vendor-supported arrangement that can enforce the policy you need.
Keep evidence for maintenance
Record the firmware, relevant settings and observed result for each test. If a necessary control is unsupported, consult the vendor’s supported alternatives or choose equipment that meets the requirement.
The acceptance criterion is the behavior of the actual clients and services. A settings screenshot is useful documentation, but it is not sufficient proof that the same boundary applies to both protocol families after an upgrade.
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.