# GL-MT6000 (Flint 2): AdGuard Home fails after 4.11 upgrade, and stays broken after rolling back to 4.9.1 (ipset.conf missing)

**URL:** <https://forum.gl-inet.com/t/gl-mt6000-flint-2-adguard-home-fails-after-4-11-upgrade-and-stays-broken-after-rolling-back-to-4-9-1-ipset-conf-missing/71705>\
**Category:** Router\
**Created:** [September 30, 2026, 8:09pm UTC](https://forum.gl-inet.com/t/gl-mt6000-flint-2-adguard-home-fails-after-4-11-upgrade-and-stays-broken-after-rolling-back-to-4-9-1-ipset-conf-missing/71705 "2026-09-30T20:09:57Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\
**Post date:** [October 1, 2026, 5:51pm UTC](https://forum.gl-inet.com/t/gl-mt6000-flint-2-adguard-home-fails-after-4-11-upgrade-and-stays-broken-after-rolling-back-to-4-9-1-ipset-conf-missing/71705/3 "2026-10-01T17:51:08Z")

</div>

Hi,

Have you followed this guide to configure the **ipset feature in AdGuard Home** so that **domain-based VPN policy routing** continues to work when **AdGuard Home Handle Client Requests** is enabled?

> [@How to Use “AdGuard Home Handle Client Requests” with VPN Domain-Based Routing on GL.iNet Routers](https://forum.gl-inet.com/t/how-to-use-adguard-home-handle-client-requests-with-vpn-domain-based-routing-on-gl-inet-routers/69988):
>
> How to Use “AdGuard Home Handle Client Requests” with VPN Domain-Based Routing on GL.iNet Routers Background GL.iNet firmware can route selected domains through a VPN Client by asking dnsmasq to add the IP addresses returned for those domains to an ipset. The VPN policy rules then match the destination IP against that set and apply the appropriate VPN routing mark. However, when Applications → AdGuard Home → AdGuard Home Handle Client Requests is enabled, DNS requests sent by LAN clients to th…

---

_[View the full topic](https://forum.gl-inet.com/t/gl-mt6000-flint-2-adguard-home-fails-after-4-11-upgrade-and-stays-broken-after-rolling-back-to-4-9-1-ipset-conf-missing/71705)._
