Wireguard client not routing any traffic on GL-MT300N-V2

akiel · 2019-12-24T00:43:53.137Z

I’m trying to route all my traffic through wireguard and failing. I have tested the configuration in other devices and it works perfectly. When I click connect on the GUI it actually connects to the server and creates the routing rules but nothing else happens. No traffic goes anywhere.
My firmware version is 3.025.

root@MT300N-V2:~# wg show
Warning: one or more unrecognized netlink attributes
interface: wg0
public key: [key]
private key: (hidden)
listening port: 55176

peer: [key]
preshared key: (hidden)
endpoint: [ip]:54321
allowed ips: 0.0.0.0/0
transfer: 0 B received, 296 B sent
persistent keepalive: every 25 seconds

root@MT300N-V2:~# ip r
0.0.0.0/1 dev wg0 scope link
default via 172.29.4.150 dev apcli0 proto static src 172.29.4.149 metric 20
[ip] via 172.29.4.150 dev apcli0
128.0.0.0/1 dev wg0 scope link
172.29.4.148/30 dev apcli0 proto static scope link metric 20
192.168.8.0/24 dev br-lan proto kernel scope link src 192.168.8.1

Can someone please assist me with this?

ThH · 2019-12-24T03:18:02.913Z

What I found very unfortunate with wireguard, is that it does not really give you an indication if the connection was established. What I have found as an indicator, that it is not connected if there are no bytes received.

Any “established” connection I had, had at least a few bytes received even if there was no traffic passing through.

I know this doesn’t really help, but maybe you could first start to find out, why connection is not really established.

akiel · 2019-12-24T09:30:01.818Z

It’s odd because I see the peer connected on the server also.

ThH · 2019-12-24T09:32:34.212Z

This could be, but the server is not responding, or the response is not received by the router.

Did you set the listen port or was it set automatically?

akiel · 2019-12-24T09:34:23.819Z

the port was set automatically

ThH · 2019-12-24T09:37:39.683Z

You could try setting it to the same port the server listens on 54321 as this was working on some configurations I had.

Could you post your redacted settings from the wireguard client page in the router interface.

akiel · 2019-12-24T09:45:50.547Z

image528×593 20.5 KB

Changing the port did not work.
Also playing with the DNS options like someone recommended in other threads is of no use.

ThH · 2019-12-24T09:52:08.080Z

Are the VPN policies active?
For me it worked best setting the IP of the local network outside the router as only “do not use” rule (If the router is connected directly to the internet the set “use only for” without setting any IP).

And I would have DNS set to 1.1.1.1 or 8.8.8.8 for testing until it runs and then take it from there.

akiel · 2019-12-25T10:06:29.520Z

I’m connected to a public hotspot with captive portal. It disconnects me every hour so I wrote a script to reconnect. The VPN policies are set so I can still access this portal with my script.

image658×631 31.8 KB

ThH · 2019-12-25T15:39:10.820Z

And the wireguard settings are functioning within that same public hotspot with another device (as a lot of public hotspots limit the open ports, which could block the tunnel)?

akiel · 2019-12-25T23:37:48.211Z

Yes, the same configuration is working on 2 other devices in the same network. (not at the same time)

ThH · 2019-12-26T22:16:48.510Z

Then I don’t have any more suggestions on what to look for.

Nevertheless, I am still assuming a connection issue rather than a routing issue as long as the received packets are 0.

akiel · 2020-01-04T15:41:58.483Z

You were correct. It was a connection problem.
I had written the wrong Preshared Key
Since for some reason I could’n import the file I was copypasting from another file and pasted the wrong key. Did not notice till today.
Now it’s wrorking.
It is anyways annoying that I don’t have access to any logs so it’s really difficult to debug when there’s a problem.
Thank you for your help.

ThH · 2020-01-04T18:47:10.774Z

No Problem, glad it’s working.