Wireguard connection drops after a couple of seconds

hcooke · 2020-01-05T09:13:48.165Z

Hi there is no pre-shared key. . I’ve just noticed that there is no persistent keep alive for the Mango client.
Will fix this and get back if this was not the problem

    option public_key 'x5Qk5gMhIN+XLNmTZWnJMnk='
	list allowed_ips '10.200.200.2/32'
	option route_allowed_ips '1'
	option persistent_keepalive '25'
	option endpoint_port '51820'
	option description 'OnePlus'

config wireguard_wg0
	option public_key 'xpmzQglyze+aQ1wI2wuErPR5nnDwY='
	list allowed_ips '10.200.200.3/32'
	option route_allowed_ips '1'
	option endpoint_port '51820'
	option persistent_keepalive '25'
	option description 'iPad'

config wireguard_wg0
	option description 'Xaomi'
	option public_key 'xL4ykRftzO/VFlPoUtkv113Kx8='
	list allowed_ips '10.200.200.4/32'
	option route_allowed_ips '1'
	option persistent_keepalive '25'

config wireguard_wg0
	option description 'Mango'
	list allowed_ips '10.200.200.5/32'
	option route_allowed_ips '1'
	option public_key 'xLv4ofuZOR8HH+AAdrmE='

hcooke · 2020-01-05T09:36:45.209Z

Corrected but same dropping of connection. ? no handshake?
Here is the corrected server config
config interface ‘wg0’
option proto ‘wireguard’
option private_key ‘XXXXXXXXXgS7LlW1FDwrztqsPiFg=’
option listen_port ‘51820’
list addresses ‘10.200.200.1/24’

config wireguard_wg0
	option public_key 'XXXXXXXXXXXQk5gMhIN+XLNmTZWnJMnk='
	list allowed_ips '10.200.200.2/32'
	option route_allowed_ips '1'
	option persistent_keepalive '25'
	option endpoint_port '51820'
	option description 'OnePlus'

config wireguard_wg0
	option public_key 'XXXXXXXXXXXXXXXXXX+aQ1wI2wuErPR5nnDwY='
	list allowed_ips '10.200.200.3/32'
	option route_allowed_ips '1'
	option endpoint_port '51820'
	option persistent_keepalive '25'
	option description 'iPad'

config wireguard_wg0
	option description 'Xaomi'
	option public_key 'XXXXXXXXXXXXX6L4ykRftzO/VFlPoUtkv113Kx8='
	list allowed_ips '10.200.200.4/32'
	option route_allowed_ips '1'
	option persistent_keepalive '25'

config wireguard_wg0
	option description 'Mango'
	list allowed_ips '10.200.200.5/32'
	option route_allowed_ips '1'
	option public_key 'DnJSfdwuP4hmc/m0YdWZwoloLv4ofuZOR8HH+AAdrmE='
	option persistent_keepalive '25'

And the Mango client confi g
config proxy
option main_server ‘XXXXXX’
option enable ‘0’

config peers 'wg_peer_6492'
	option name 'XXXXXXXX'
	option address '10.200.200.5/32'
	option private_key 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX='
	option dns '192.168.3.1'
	option end_point 'XXXXXXXXXXXX.duckdns.org:51820'
	option public_key '19StB1m9/apAWznWH2dIYLMgPZVjvRUDx1CHvrnCATA='
	option allowed_ips '0.0.0.0/0'
	option persistent_keepalive '25'
	option listen_port '51820'
	option mtu '1420'

At the server the connection looks like this

**Public Key:** DnJSfdwuP4hmc/m0YdWZwoloLv4ofuZOR8HH+AAdrmE=
**Endpoint:** xxx.205.241.88:51820
**Allowed IPs:**
• 10.200.200.5/32
**Persistent Keepalive:** 25s
**Latest Handshake:** Sun, 05 Jan 2020 09:28:47 GMT (5m ago)
**Data Received:** 404 B
**Data Transmitted:** 6 KiB

Any solution?

rp201rp · 2020-01-05T10:23:24.386Z

using your android client, export your working config to a .conf and cut and past settings in client connection on 300n. if it works then manually gerenerate new client keys and place in openwrt and substitute in 300n in /etc/config/wireguard. You can cheat and use same settings for server and clients from 1300. and oh yeah dont forget to disable your other client connections while testing.

hcooke · 2020-01-05T12:14:51.024Z

That’s essentially how I set it up! It does connect so those settings are basically OK

rp201rp · 2020-01-06T01:25:08.535Z

my last try is in your openwrt router go to luci/network/interfaces and wg0 and make sure mtu is set for 1420

bOcy · 2020-01-06T07:53:09.546Z

i would check your config on the mango’s “wireguard client” again, a wrong “allowed ip/prefix” would let you connect to the wireguard server but unable to establish connection

hcooke · 2020-01-06T16:11:45.116Z

Checked MTU and allowed IP. Still only the initial handshake. It takes minutes before the abort option becomes available.

bOcy · 2020-01-07T14:55:37.001Z

10.200.200.1/24

Try your interface listed address 10.200.200.1/32

hcooke · 2020-01-08T15:27:57.558Z

Not sure what you mean. I’ve changed the address in the interface section of the Mango client gui to 10.200.200.5/24 (was that what you intended?) which fits with the exported config from the android app but the connection still drops. If I change the wg0 openwrt interface to 10.200.200.1/32 the wg connection stays up but there is no internet.
Sorry for the confusion

ThH · 2020-01-08T18:00:23.946Z

Looking at server config I thought the same like bOcy. option list_addresses should be 10.200.200.1/32 instead ‘10.200.200.1/24’ to my opinion.

If the connection stays up, are there more packets exchanged?
How do the redacted settings look in mango web interface?

bOcy · 2020-01-09T07:17:29.116Z

put everything with /32

except 0.0.0.0/0, this one remains

mango wireguard600×905 18.5 KB

ThH · 2020-01-09T11:30:08.087Z

For what reason did you set the listen port? Tried without or by setting the same port as used on server (51820)?

If you have 10.200.200.1/32 set on server and the connection stays up, are are there packets sent and received by mango?

bOcy · 2020-01-09T11:54:00.416Z

Listen port on the mango is optional (random)

hcooke · 2020-01-09T12:31:28.033Z

If I have 10.200.200.1/32 set on the server the connection stays up for ~5min, about 600 packets are sent over a period of 3min, there is no internet connection on Mango. The android peer connects but similarly has no internet connectivity. Again, the android and iOS peers work perfectly with the server set to 10.200.200.1/24.
I set up wireguard on openWRT according to this http://chrisbuchan.co.uk/uncategorized/wireguard-setup-openwrt/

rp201rp · 2020-01-09T12:48:19.268Z

any chance that it’s not that it’s the only client disconnecting, but rather the only one thats not reconnecting after firewall rule,or event every so often causing disconnect?

hcooke · 2020-01-09T13:51:00.716Z

I wondered if it was a firewall problem but I wouldn’t know where to start with that.

ThH · 2020-01-09T17:02:19.743Z

What you could try is to set up a wireguard server on the mango with the gui and compare in the lucy settings of the mango with the settings in your openwrt router.

Additionally, looking at the mango config and comparing it to the instructions on the page you linked, it also suggests to use 10.200.200.2/24 in the client app, while you have set 10.200.200.3/32, so if the instructions are right (which doesn’t fit to my working setting), you could try that.

Edit: I have to revoke to what I’ve written. My server also has /24 in the end.

hcooke · 2020-01-09T17:49:26.138Z

My reading of the guide is /32 for peers –
In the PEERS section click Add and paste in the Public key you obtained from the wireguard app. In the Allowed IP’s section you’re indicating what addresses are reached through the tunnel to this peer. In our example we only want to send traffic to the one client’s address. To do this, pick an IP address for the client in the subnet you previously chose, and use /32 at the end. For example 10.200.200.2/32.–
I’ll try setting up a server on the Mango

ThH · 2020-01-09T18:00:50.655Z

You are right for the server configuration section, but the mango is the client and below it states:
“Go back to the app and in Addresses , put the address you chose for the client and entered on the server in the peer Allowed IPs section, but use the real subnet mask (/24 in CIDR notation) like you did for the server Address, e.g. 10.200.200.2/24.”

hcooke · 2020-01-09T18:39:09.942Z

You are right, thanks for your patience. I get confused by peers, clients and servers in wg.