How to use DoT/DoH on Flint 2 router with T-Mobile 5G WAN

Installing and Using OpenWrt
1

How do I effectively use GL.iNet Flint 2 (OpenWRT) wifi router with a local IP for its WAN input from the T-Mobile 5G Home Internet while enabling IPv6 on the Flint 2 router to reduce latency and increase performance since this is the only way to bypass the double/triple NAT issue? Also, TMobile home internet is a Carrier-Grade NAT (CGNAT) so it's not even possible to make the Flint 2 get a public IP address from the TMobile gateway to the Flint 2's WAN.
Would Flints Drop in Gateway feature work? I'm so lost and don't want the Flint 2 router being in AP mode because then all of its features become null and void.

I'm trying to use either ControlD DoT via the GL.iNet interface --or-- the CTRLD DoH daemon. Which would be better for this and how to get it to encrypt and filter traffic with IPv6 (because TMobile is an IPv6 only network, and using only IPv4 on Flint reduces performance) enabled on Flint?

Please help! Thank you for your attention to this matter.

  • Alexander B.
2

The GL.iNET software is a heavily modified and outdated fork of OpenWRT.
Unfortunatley we do not have expertise on this forum about it.
So you better ask at the GL.iNet forum or install genuine OpenWRT.

1 Like
3

677
6771440×3168 245 KB

This is the OpenWrt version

4

No unfortunately it is not, it is the GL.iNet fork, as said outdated and heavily modified.

Please ask your questions at the GL.iNet forum.

4 Likes
5

Install official Openwrt release or ask gl.inet.

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.