Cannot connect Slate router using Wireguard to Android phone

kyson-lok · 2018-12-10T02:37:36.575Z

Does the IP address in endpoint is the same as the IP address you see on admin web? Could you take a screenshot on INTERNET tab? It looks like this.

image1105×692 118 KB

NJKA · 2018-12-10T19:11:15.546Z

PNG2410×1461 345 KB

Should the IP Address shown be a public one?
The modem attached via the USB slot is a ZTE MF730 model. Even though the docs describe it’s a modem, The Slate always tethers the device and it never shows up in the 3G/4G Modem section.

Many Thanks

kyson-lok · 2018-12-11T03:37:27.572Z

NJKA:

attached

It is a private IP address, not public IP address. Therefore, the WireGuard client fails to connect your Slate which is act as server.

alzhao · 2018-12-11T05:14:36.480Z

If it work in tethering mode, it should have its own UI on 192.168.0.1

You can set up port forward in the modem.

But most importantly, make sure your carrier allows you to use as server. This is generally not possible in carriers.

NJKA · 2018-12-11T11:05:39.668Z

Ok, forgive my noob questions, trying to understand all this.

So these USB dongles are’t pure modems. There modems + router and without forwarding, the packets on port 51820 won’t get though, is that correct? Unfortunately the dongle does not have a port forward config page and is not accepting ssh requests.

Can you get pure USB mobile modem that will provide the Slate with just a public IP. If so, any recommendations?

Do I need the Slate to also have a public IP (rather than private tethered one) if I use the Slate a WireGuard client, and not as a server?

Thanks

kennethrc · 2018-12-11T20:57:38.341Z

NJKA:

Can you get pure USB mobile modem that will provide the Slate with just a public IP. If so, any recommendations?

Problem is, that’s up to the carrier, unfortunately. Almost every provider (in the US, at least, YMMV) will (CG)NAT all consumer-grade mobile connections (and some even CGNAT IPv6!). You’d have to see if your carrier will allow you to get a static IP for your account, but then you may venture into Enterprise-grade territory and I have no idea what pricing is for that.

daddo · 2019-05-27T21:20:03.441Z

Did i get that right: WireGuard server is useless or not usable as additional encryption layer for wireless (without public ip with neccesary ports open on WAN/ISP side)? Why? There has been issues with WPA* and i decided that i want to use the WireGuard server as extra security measure from my mobile device to GL device where “wired network begins” even when i use GL device in WISP mode in hotel, behind their network without ports forwarded (to GL device). So yes, i also expected that after turning WireGuard server on and configurating mobile devices connected to the same device over wireless with QR code work out of the box - even if there is no internet connection on wan side at all…

Johnex · 2019-05-27T21:24:12.573Z

Well no.

If you are connecting using the wireguard client from a phone in your local network to a remote wireguard server, hosted in a datacenter or using one of the wireguard providers, you can connect using your internet without having to open ports.

You only have to open ports and need a public ip if you want to connect FROM OUTSIDE to your home network with a wireguard server running on your network or router.

Also don’t think that the LAN port in a hotel room or another place is secure. I can sit in the room next to you, use some packet sniffing and ARP injection to capture your data since hotels usually have a switch to deliver the internet to the rooms. Protecting the wifi won’t help if you don’t secure out to the net too.

daddo · 2019-05-27T21:55:44.068Z

Like i said, i mean that even without having an remote WireGuard server (or it’s subscription) it should be possible to have wireguard tunnel as short as from GL wireless clients to the GL itself and that’s all(only on scenarios when there is no public ip and open ports- it would be more useful than now, like described in first post). New feature request maybe?

But about remote connection from remote site into device behind in my home network without open and redirected ports: i have seen that for example one of dahua network camera has such “P2P functionality”, that you can connect your android client to the camera even when the ports are closed. As i understood, it worked somehow that the camera itself initialized an connection to some kind of (manufacturer) middle-service and when android client requested an connection the those two were somehow bounded like it was response to the request made by camera itself.

GL has some DDNS functionality and server for that. It would be awesome, when you can implement something similar: GL router initializes outgoing connection to it and when remote client wants to connect then it will be somehow added to already made connection from inside to public network. You can imagine the numbers of clients all over the world, who’s ISP doesn’t offer open ports and public ip with fair price…

Johnex · 2019-05-27T22:00:19.808Z

GL will make a service like that but it is not ready yet.

daddo · 2019-05-27T22:10:34.241Z

Ok, any information when will i be much happier GL owner than i allready am?
Will it work with every model which allready support WireGuard server?

Johnex · 2019-05-27T22:11:45.967Z

No time frame at the moment that i have heard of, just seen Alfie mention it in another thread. He also said that it should work with all routers that can run v3 firmware.

woolverton · 2019-07-20T01:08:42.513Z

I’m having the same problem as the original post but I do have an external IP.

Slate router, Mango 3.026, connected to fiber modem via Ethernet.
GL UI reports the IP address as 42.xxx.yyy.zzz. Gateway is 42.xxx.yyy.254.

DDNS gl-ddns 3.0.21: installed and enabled: pnXYZ.glddns.com

DNSWireGuard Server 4.14.63/20181119 running and using default settings.
Client setup using default settings: 10.0.0.2/32; listen 8521; DNS 64.6.64.6,

WireGuard iPhone Client 0.0.20190609.
Add a Tunnel: Client settings transferred to iPhone using QR code; no edits.
Endor: 42.xxx.yyy.zzz:51820; 10.0.0.2/32; Listen 39877; DNS 64.6.64.6

Client settings IP

WG Client not connected (cellular, WiFi off): data flows ok
WG Client connected (cellular, WiFi off): no data flows

Edit Client settings to DDNS address pnXYZ.glddns.com:51820

activate WG Client: error— DNS resolution failure…

Delete Client settings. Reinstall via QR:

WG Client not connected (cellular, WiFi off): data flows ok
WG Client connected (cellular, WiFi off): no data flows

Any advice?

Note: OpenVPN server and client work correctly using default settings.

woolverton · 2019-07-26T13:08:21.007Z

Is this loopback Server address the issue?
[address circled; screen shot is of iOS client—> VPN Status—> info ]

fty%20vpn1133×1595 261 KB

kyson-lok · 2019-07-29T06:19:08.667Z

Did you configure port forwarding on your main router?

Could you please also take a screenshot of WireGuard page on your iPhone?

woolverton · 2019-07-29T07:17:46.870Z

This router is the main router.

Screenshots [keys and IPs deleted]
Wireguard settings (as created by QR code):

IMG_13161125×2436 274 KB

iOS VPN settings

IMG_13171125×2436 154 KB

notes:
• the router is on an external IP.
• Clients can connect but no data moves through.

alzhao · 2019-07-29T15:49:53.564Z

can you change the server port from 51820 to one low port, e.g. 1080 etc.?

Also when you use this, do not connect to the router which is the server at the same time, use your carrier data and try.

When you are connect to the Wireguard server’s wifi and want to connect to the Wireguard sever at the same time, it may not work. Of course it does not make sense because you are in its direct wifi network.

So when you set up a Wireguard server, alway turn off your phone’s wifi and use your carrier data to test. This is what you will do when you travel.

woolverton · 2019-07-30T00:14:29.836Z

Changing the port does not resolve the issue— still no data through.

notes:

when testing I am using only cellular only; wifi is off.
The screen caps above were taken hastily for posting here.
This WireGuard connection issue described above occurs on two nearly identical systems: outside IPs, Hong Kong Telecom/Netvigator fibre, same client set, only difference: one is GL Mango, another is GL Slate (both on latest FW.) (Yes, I’m using different login credentials for each server.)
These routers work correctly in all aspects including OpenVPN server but not working for WireGuard server.

IMG_13191125×2436 120 KB

IMG_13201125×2436 185 KB

woolverton · 2019-07-30T01:39:03.924Z

After Starting WireGuard server, are the Firewall Zones default settings correct ?

Leo · 2019-07-30T04:03:08.269Z

I has just tested wireguard server feature on Mango(GL-MT300N-V2), it work.
Mango firmware version: openwrt-mt300n-v2-3.026-0729.bin,
Port forward 51999,
WireGuard for Android v0.0.20190605
Android Phone use carrier data.

After starting wireguard server, default settings of the Firewall Zones are correct.

When you start wireguard server at home, did you use your phone ( use carrier data ) to test it immediately?

PS: wireguard is not designed to across the gfw, so if you use it in mainland china, it may not work.