Locked out of GL.iNet admin panel after WireGuard route change

[oooohhhhhhh]

Hi everyone,
I’m looking for help with a WireGuard routing issue on my GL.iNet router.

Access Client LAN from Server (WireGuard) - GL.iNet Router Docs 4

• I set the Target Address to 192.168.8.0/24.
• I set the Gateway to 10.1.0.1.
• After applying this, devices can still connect to the GL.iNet Wi-Fi, but there is no internet access.
• The router’s admin panel at http://192.168.8.1/ is no longer accessible.

Has anyone experienced this before, or can explain what went wrong and how to recover access without a full reset?

Thanks in advance for any help.

[will.qiu]

Hi

@oooohhhhhhh

Has anyone experienced this before, or can explain what went wrong

It appears you have specified a route for the local subnet to the tunnel at the remote end, which is preventing access to the local subnet?

Please note that the destination address should be configured as the subnet of the remote router rather than the local subnet.

@oooohhhhhhh

how to recover access without a full reset?

Please try holding down the Reset button for more than 4 seconds but no longer than 10 seconds to reset only the network settings.
If it doesn't work, we may have to completely restore it to factory settings.

Repair network or reset - GL.iNet Router Docs 4

[oooohhhhhhh]

Thank you, a short reset worked!

But how do I set up the routing correctly on the WireGuard router? What should the Target Address and Gateway be if my LAN is under 192.168.8.0/24, and my mobile client with the WireGuard client has a client IP of 10.0.0.2/24?

[will.qiu]

To help us better understand the situation and provide the correct settings, could you please clarify your specific goal? It would be very helpful if you could draw a simple network topology diagram that includes:

• Devices: The WireGuard server, the mobile client, and any LAN devices you are trying to reach.
• IP Addresses & Subnets: Labeled for each router and local network (e.g., 192.168.8.x).

Based on your current description, it appears you want to use a mobile client (like a smartphone) to access LAN devices located behind the WireGuard server.
If our understanding is correct, enabling "Allow Remote Access to the LAN Subnet" should suffice.

[oooohhhhhhh]

@will.qiu

Based on your current description, it appears you want to use a mobile client (like a smartphone) to access LAN devices located behind the WireGuard server.

Yes this is exactly what I’m trying to do.

@will.qiu

If our understanding is correct, enabling "Allow Remote Access to the LAN Subnet" should suffice.

however this does not work.

I’m not familiar with network topology diagram but I have tried my best

One thing to not is after starting wireguard server I don’t see anything under VPN Dashboard

[oooohhhhhhh]

[will.qiu]

Oh, sorry, I attached the wrong screenshot.

Please refer to this one instead:

After enabling it, you should be able to use the 192.168.8.3 to access the NAS on your phone.

[oooohhhhhhh]

Thank you! This works!

[oooohhhhhhh]

If this can be easily done with a single click, what’s the purpose of routing?

[will.qiu]

That scenario is for WireGuard Site to Site, where the server required accesses client resources (opposite to your situation).

[oooohhhhhhh]

Thank you!