# Tailscale on GL-MT3000 issues after upgrade

**URL:** <https://forum.gl-inet.com/t/tailscale-on-gl-mt3000-issues-after-upgrade/43281>\
**Category:** Router\
**Created:** [June 6, 2024, 3:58pm UTC](https://forum.gl-inet.com/t/tailscale-on-gl-mt3000-issues-after-upgrade/43281 "2024-06-06T15:58:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tinfins](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/e79b87/32.png) [@tinfins](https://forum.gl-inet.com/u/tinfins)\
**Post date:** [June 6, 2024, 3:58pm UTC](https://forum.gl-inet.com/t/tailscale-on-gl-mt3000-issues-after-upgrade/43281/1 "2024-06-06T15:58:15Z")

</div>

I am using my router to route traffic through a Tailscale exit node. I recently updated my MT3000 to firmware 4.5.16. I also updated Tailscale to 1.66.4 via [this script](https://forum.gl-inet.com/t/script-update-tailscale-on-nearly-all-devices/37582).

Before I did this, I was using the DNS method described [here](https://forum.gl-inet.com/t/tailscale-and-block-non-vpn-traffic/30493/11). Since the upgrades, I've found that that no longer works. Actually, even if I set DNS to automatic, none of the devices connected to the MT3000 get internet access. The only thing that works right now is setting the DNS manually to any well-known provider.

Is there a way I can get back the previous functionality without downgrading? Not sure if it's related to this [post](https://forum.gl-inet.com/t/mt3000-internet-breaks-when-upgraded-version-of-tailscale-exit-node-is-enabled/42127), but I am on version 1.66.4 which that post says is working.

 ![netdiagram](https://forum-static.gl-inet.com/original/3X/6/e/6e2088f84dff7f139ec829a40c369d9d69aa65a2.jpeg)

---

<div class="post-metadata">

**Author:** ![tinfins](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/e79b87/32.png) [@tinfins](https://forum.gl-inet.com/u/tinfins)\
**Post date:** [June 8, 2024, 10:59pm UTC](https://forum.gl-inet.com/t/tailscale-on-gl-mt3000-issues-after-upgrade/43281/2 "2024-06-08T22:59:37Z")

</div>

Update:

I also had some other issues tunneling to a VPN on machines connected to the MT3000, as well as many issues with Microsoft single-sign-on services. I downgraded Tailscale on the MT3000 to 1.58.2, which solved those issues. I still need to manually set a public DNS server, but at least I can access all services.

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [June 11, 2024, 3:39am UTC](https://forum.gl-inet.com/t/tailscale-on-gl-mt3000-issues-after-upgrade/43281/3 "2024-06-11T03:39:34Z")

</div>

This issue (I am not sure if it is a issue/problem) probably required to capture the data package by the Wireshark, to see if the detail info of the DNS (port 53) service from server to client, or vice versa, but I could not reproduce this situation.

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [October 29, 2025, 11:39am UTC](https://forum.gl-inet.com/t/tailscale-on-gl-mt3000-issues-after-upgrade/43281/4 "2025-10-29T11:39:35Z")

</div>


