# AXT1800 lost remote access to local LAN interface IP

**URL:** <https://forum.gl-inet.com/t/axt1800-lost-remote-access-to-local-lan-interface-ip/63871>\
**Category:** VPN, DNS, Leaks\
**Created:** [September 10, 2025, 2:02pm UTC](https://forum.gl-inet.com/t/axt1800-lost-remote-access-to-local-lan-interface-ip/63871 "2025-09-10T14:02:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![9b9e69c2-4b75-4420](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/9/a587f6/32.png) [@9b9e69c2-4b75-4420](https://forum.gl-inet.com/u/9b9e69c2-4b75-4420)\
**Post date:** [September 10, 2025, 8:47pm UTC](https://forum.gl-inet.com/t/axt1800-lost-remote-access-to-local-lan-interface-ip/63871/2 "2025-09-10T20:47:55Z")

</div>

I'm going to shoot from the hip & say 'Allow Remote Access the LAN Subnet' got toggled off in the drastic change in firmware that introduced PBR. Look for the 'gear' icons for your tunnels in the VPN Dashboard.

 ![Screenshot_20250910_202708](https://forum-static.gl-inet.com/original/3X/e/0/e07ef09c806cb0ad5f5a9a3d69584ab43bd66587.png)

I'd also check the WG configuration routes are still as expected. See below for ideas/approaches:

> **[Access Client LAN from Server (WireGuard) - GL.iNet Router Docs 4](https://docs.gl-inet.com/router/en/4/tutorials/wireguard_server_access_to_client_lan_side/)**
>
> Documentation for GL.iNet Router Productions

> **[Access Server LAN from Client (WireGuard) via domain name - GL.iNet Router...](https://docs.gl-inet.com/router/en/4/tutorials/how_to_access_server_lan_device_via_domain_name/)**
>
> Documentation for GL.iNet Router Productions

> [@Flint 2 4.7.7 to 4.8.2 broken](https://forum.gl-inet.com/t/flint-2-4-7-7-to-4-8-2-broken/63688/15):
>
> Here's confirmation the Flint v2 (GL-MT6000) v4.8.0's dnsmasq behavior is changed per GL.iNet support staff:

---

_[View the full topic](https://forum.gl-inet.com/t/axt1800-lost-remote-access-to-local-lan-interface-ip/63871)._