Why would THIS Wireguard Config Change be needed with GL.iNet?

Technical Support for Routers
1

Hi everyone,

I have a Unifi Dream Machine Pro.

I’ve set up a Wireguard Server to be able to connect back home when away.

I’ve uploaded the config file that was generated by the UDM Pro for my Gl.iNet AC1200, it looked like this:

[Interface]
PrivateKey = xxxxxxxx
Address = 192.168.3.7/32
DNS = 1.1.1.1,8.8.8.8

[Peer]
PublicKey = xxxxxxxxxxx
AllowedIPs = 192.168.3.1/32,192.168.3.7/32,0.0.0.0/0
Endpoint = xxx.xxx.xxx.xxx:xxxxx

I enabled the VPN and turned on the internet Kill Switch to force everything through the VPN.

I could ping 192.168.3.1 but could NOT access the internet. Nothing would work until I changed the AllowedIPs = 0.0.0.0/0 only. In otherwords, the config file looked like this:

[Interface]
PrivateKey = xxxxxxxx
Address = 192.168.3.7/32
DNS = 1.1.1.1,8.8.8.8

[Peer]
PublicKey = xxxxxxxxxxx
AllowedIPs = 0.0.0.0/0
Endpoint = xxx.xxx.xxx.xxx:xxxxx

Why would THAT make a difference, especially since 0.0.0.0/0 was already a part of the allowed ips?

Thanks

2

For 3.x firmware, 0.0.0.0/0 must be in the first place of AllowedIPs.
If 0.0.0.0/0 is there, then 192.168.3.1/32,192.168.3.7/32 is not needed actually.

3

Thanks for the reply.
I get that having the other IP addresses there would be redundant if 0.0.0.0/0 was included in the list of IP’s . . . but I would have thought it wouldn’t matter as long as it was “IN” the list. Is this a Wireguard thing or a GL-iNet thing?

I just looked on my phone and I happen to have the other IP ranges included before the 0.0.0.0/0 (it’s just the config file my WG server gave me - I didn’t add it on purpose), and it connects every time without issue.

I’m happy that it’s connecting - I’m just trying to gain a little understanding with this question.

4

It’s 3.x firmware bug. If your model of GL.iNet router has 4.x firmware, you can try upgrade.

5

Yeah change allowed ips to 0.0.0.0/0 or however you have it above and upgrade to something 4.x if your router has it. You may need to download and upload via the router as opposed to a auto upgrade through the app.

1 Like
6

I was sure that I tried this on the GL Slate and I had the same problem.
I’ll test when I get a chance and report back.
My GL Slate is running Firmware 4.4.6