GL-MT300N-V2 WireGuard

Hi all,
I’m using GL-MT300N-V2 router to create a VPN server with WireGuard.
I followed all the guides but when i connect to the VPN using the windows client i can not ping anything in the LAN of the Mini router.
Anyone can help me?

Many thanks

Turn on:
(firmware 3.x) WireGuard® Server - Allow Access Local Network

(firmware 4.x) VPN Dashboard - VPN Server - Options - Allow Remote Access LAN
image

I already did it but nothing change…
Thanks for the answer

Are there any firewalls on the devices you are trying to ping active?
Is there a device which does not have a real operating system (like a webcam, printer, sth. like this) so you could try to ping this? Can you traceroute it as well and post the results?

I can not ping anything, i have problem to ping the endpoint also.
I can not enter on the setup page of the router via WireGuard.

1 Like

Is the Wireguard tunnel up? Or are there any problems within the logs?

2023-12-06 11:42:29.867671: [TUN] [Prova] Starting WireGuard/0.5.3 (Windows 10.0.19045; amd64)
2023-12-06 11:42:29.867671: [TUN] [Prova] Watching network interfaces
2023-12-06 11:42:29.868699: [TUN] [Prova] Resolving DNS names
2023-12-06 11:42:30.080620: [TUN] [Prova] Creating network adapter
2023-12-06 11:42:30.296967: [TUN] [Prova] Using existing driver 0.10
2023-12-06 11:42:30.307321: [TUN] [Prova] Creating adapter
2023-12-06 11:42:30.794764: [TUN] [Prova] Using WireGuardNT/0.10
2023-12-06 11:42:30.795281: [TUN] [Prova] Enabling firewall rules
2023-12-06 11:42:30.601100: [TUN] [Prova] Interface created
2023-12-06 11:42:30.797840: [TUN] [Prova] Dropping privileges
2023-12-06 11:42:30.797840: [TUN] [Prova] Setting interface configuration
2023-12-06 11:42:30.798352: [TUN] [Prova] Peer 1 created
2023-12-06 11:42:30.799373: [TUN] [Prova] Sending keepalive packet to peer 1 (2.32.144.250:51820)
2023-12-06 11:42:30.799373: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:42:30.800875: [TUN] [Prova] Monitoring MTU of default v6 routes
2023-12-06 11:42:30.800875: [TUN] [Prova] Interface up
2023-12-06 11:42:30.810818: [TUN] [Prova] Setting device v6 addresses
2023-12-06 11:42:30.815164: [TUN] [Prova] Monitoring MTU of default v4 routes
2023-12-06 11:42:30.816050: [TUN] [Prova] Setting device v4 addresses
2023-12-06 11:42:30.826121: [TUN] [Prova] Warning: the “Ethernet” interface has Forwarding/WeakHostSend enabled, which will cause routing loops
2023-12-06 11:42:30.843933: [TUN] [Prova] Startup complete
2023-12-06 11:42:35.931010: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:42:40.988827: [TUN] [Prova] Handshake for peer 1 (2.32.144.250:51820) did not complete after 5 seconds, retrying (try 2)
2023-12-06 11:42:40.988827: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:42:46.114459: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:42:51.150430: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:42:56.155789: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:01.190201: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:06.198894: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:11.213451: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:16.294733: [TUN] [Prova] Handshake for peer 1 (2.32.144.250:51820) did not complete after 5 seconds, retrying (try 2)
2023-12-06 11:43:16.294733: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:21.321748: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:26.417726: [TUN] [Prova] Handshake for peer 1 (2.32.144.250:51820) did not complete after 5 seconds, retrying (try 2)
2023-12-06 11:43:26.417726: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:31.513348: [TUN] [Prova] Handshake for peer 1 (2.32.144.250:51820) did not complete after 5 seconds, retrying (try 2)
2023-12-06 11:43:31.513348: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:36.558389: [TUN] [Prova] Handshake for peer 1 (2.32.144.250:51820) did not complete after 5 seconds, retrying (try 2)
2023-12-06 11:43:36.558389: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)
2023-12-06 11:43:41.570058: [TUN] [Prova] Handshake for peer 1 (2.32.144.250:51820) did not complete after 5 seconds, retrying (try 2)
2023-12-06 11:43:41.570058: [TUN] [Prova] Sending handshake initiation to peer 1 (2.32.144.250:51820)

Seems i have problem with the handshake

For me, it looks like the port 51820 isn’t reachable.

Is there another router active, like your MT300N is behind another one?

@matteonico did you port forward 51820 to gl-mt300n device if its behind router in home

@admon
nevermind : found ip from repeater
but the ip was changing ,i was able to port forward and test but getting handshake issues
to rule out repeater issue,used ethernet wire and still same wireguard client connection issue,
wireguard vpn server did startup ok

2024-02-10 00:43:37.179732: [TUN] [x1carbon] Setting device v6 addresses
2024-02-10 00:43:37.221321: [TUN] [x1carbon] Warning: the “Wi-Fi” interface has Forwarding/WeakHostSend enabled, which will cause routing loops
2024-02-10 00:43:37.505448: [TUN] [x1carbon] Startup complete
2024-02-10 00:43:52.268104: [TUN] [x1carbon] Retrying handshake with peer 4 (47.188.xxx.xx:51820) because we stopped hearing back after 15 seconds