Locked out of GL.iNet admin panel after WireGuard route change
from tatoko556@reddthat.com to selfhosted@lemmy.world on 06 Jan 07:02
https://reddthat.com/post/57595785

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

docs.gl-inet.com/…/wireguard_server_access_to_cli…

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.

#selfhosted

threaded - newest

eleijeep@piefed.social on 06 Jan 10:23 next collapse

Is it now handing out IPs in a different subnet? Check the IP given to your client.

tatoko556@reddthat.com on 06 Jan 12:11 collapse

it is still under 192.168.8.0/24

JoeKrogan@lemmy.world on 06 Jan 10:50 next collapse

Try connect with ethernet to access the admin page ?

If that doesnt work another option is to hard reset the router

tatoko556@reddthat.com on 06 Jan 12:10 collapse

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?

JoeKrogan@lemmy.world on 06 Jan 14:20 collapse

No worries,

I use dns for my wireguard endpoint so it hits myserverurl:50001 . Im using the router as a wg client however connecting to my server.

I have ip tables rules my server. To route connections. Its been a while but I used this back in the day when I set it up

miguelmota.com/…/getting-started-with-wireguard/

tatoko556@reddthat.com on 07 Jan 08:05 collapse

thanks a lot

tychosmoose@lemmy.world on 06 Jan 10:51 collapse

That rule is supposed to be set on the “server” at the other end of the wg connection, using its own wg address as gateway. Not on the router for the lan you’re trying to access. That seems like a pretty easy mistake to make given that documentation.

You could try a short reset of just the network configuration. Hold reset for like 5 seconds. Might need to do a full reset (10+ seconds) if that doesn’t get you back in.

tatoko556@reddthat.com on 06 Jan 12:10 collapse

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?

tychosmoose@lemmy.world on 06 Jan 13:46 collapse

So you have a single mobile device connecting via wg, correct? Not a second network?

If so the only configuration you should need on the router are firewall rules to allow forwarding from wg to lan. I am guessing that’s what the second step in the GL-iNet help accomplishes. That’s what I would recommend trying.

If I was doing this on “normal” OpenWRT I would create a firewall zone wg, and allow traffic to/from it and lan.

On the client device you should be good to go without changes if AllowedIPs is set to 0.0.0.0/, ::/0 (sending all traffic through wg).

tatoko556@reddthat.com on 07 Jan 08:05 collapse

thanks a lot