Dynamix WireGuard VPN


bonienl

Recommended Posts

On 11/10/2020 at 6:11 PM, yogy said:

I FOUND A SOLUTION!

yes, I'm answering to myself but hopefully others will find this useful.

If you are using Wireguard VPN app for Windows OS and try to connect to unRAID using Remote tunneled access here is a solution

This issue of broken local network routing appears to only happen in WireGuard for Windows.

You just saved my evening

Link to comment

I have been trying for ages now to setup WG to access my dockers on my VLAN

Local access works fine!

I suspect it is something i'm missing in pfSense!

Here are my unraid settings:

eth0.thumb.png.e0b99bb3d64611ddf1433e477ba879c2.png

 

docker.thumb.png.b7363debeba9669c69c7fb98fcc54c44.png

 

Tunnel.thumb.png.5f9dd1fac2b9d4222b8dbd1242401b0e.png

 

And pfSense setting:

gateway.png.d73a5419f14816f19e6df968dc3ed014.png

 

219675626_staticroute.png.f7c4b9ffca17f78c9168d5cde5abdfd7.png

 

Anyone see anything obvious i have missed? I've read thru a number of threads and just cant pin point my issue

Thanks

Edited by bdydrp
Link to comment

Hello all,

 

I'm trying to setup my WireGuard VPN to work with my Pihole docker running on the same box.

 

I tried to configure PiHole to run on a separate NIC, but I couldn't get it to recognize the bridged connection I created on the separate NIC in order to select it.

 

So, I read through the thread more, and I made it to the point of enabling host access to custom networks in Docker settings. This allows me to now access PiHole over WireGuard on the same NIC, but if I try to access the internet with the VPN connected, it is unable to resolve any host name.

 

How can I get my internet to work on the device with the VPN connected now?

 

Default Gateway: 10.100.1.1

Unraid IP: 10.100.1.3

PiHole IP: 10.100.1.2

 

Static route setup on router:

image.png.7f6bfb33fb430712d20faaa50d3b13a3.png

 

WireGuard setup:
image.thumb.png.c3121d8d11d6f15cd5ca8227e3d27905.png

Edited by carnivorebrah
Link to comment

If your Pi hole isn't your DNS Server, then the Peer DNS server should be your router or something else (default gateway). In this case try to put 10.100.1.1 and not 10.100.1.2 as in the picture above.

Don't forget to scan your code again (if you're using your mobile device) when you change this setting.

  • Thanks 2
Link to comment
2 hours ago, yogy said:

If your Pi hole isn't your DNS Server, then the Peer DNS server should be your router or something else (default gateway). In this case try to put 10.100.1.1 and not 10.100.1.2 as in the picture above.

Don't forget to scan your code again (if you're using your mobile device) when you change this setting.

I'm a complete idiot. I forgot to redownload the new config onto my devices. This fixed it.

 

It's always the little things...

 

*facepalm*

 

Thank you!!!

Link to comment

Hi,
 

Im looking to run Wireguard in conjunction with the Pihole container and was wondering if it's possible to select another NIC other than the standard br0. Alternatively, is there a best way to set everything up? I can connect via my phone to the tunnel but receive resolution errors as, I'm assuming, the remote client isnt communicating with pihole. Thank you. Is there a best practice of setting the two up if I have two NICs?

Link to comment

hello it possible to setup wirequard with unraid/docker as following?

 

cloud.mydomain.org ---> external root-server with ipv4/wirequard  ---->----tunnel --->---> unraid-docker service like nextcloud.

 

why I ask, due to IPS change, I have no reachable ipv4 adress. and I need this for mapping of domains my nexcloud services @ unraid

Link to comment
  • 2 weeks later...

Still having issues with this!! Can only access devices on main lan not VLANS

I have done a traceroute from my peer device (android tablet) with wifi off and WG on.

And noticed that the hop goes to a completely different network

1st hop - 10.252.52.102

2nd hop - 10.252.52.106

3rd, 4th, etc - No response

 

The Local tunnel address is 10.253.0.1      Where would 10.252 come from?

 

Link to comment
  • 3 weeks later...

So, i studied this Topic many Times. And though i'm no english native but i still think i understand everything right.

If my router is some kind of cheap enduser ISP stuff which lacks the possibility of custom routing or routes in general and all i can set up is simple NAT i have no chance to access all my Docker container through Wireguard?

My Setup is quite simple. I have 2 NICs, one (br0) for the UnRaid Webfrontend and Wireguard etc. and the other (br1) is used for all Docker container with custom IP addresses in my LAN. I use one subnet for everything in my LAN. 192.168.0.0/24.

I'm not talking about DNS i can't even ping my Docker container on their own IP. So i initially thought it would be enough to seperate the Wireguard interface from the Docker interfaces. But this was not the trick, so i read this thread and the only thing i'm missing is the custom route in my router which i can not set. What are my options now? 

I could be so convenient to connect to Wireguard, open my Heimdall-Docker and get everywhere i want (Homekit, DIYHue, Plex, Nextcloud, etc.). But i can't get it to work.

Or am i missing something?

Link to comment

I'm having some trouble after installing and uninstalling this docker. 

 

My box no longer has DNS access to anything it seems, none of the VMS either. I can RDP to them all but for somereason I cannot browse any web content on the VM's in the APPS directory of UNRAID I also can't solve anything. 

 

Could this be a simple reboot?

Link to comment

I am not getting a handshake from WireGuard client on macOS. Used to be able to connect no problem, is there a common issue occurring atm after the latest client update?

 

Edit: Regenerated keys and tried to reconnect, still same issue. Able to connect, no data, no handshake. No idea what to do next. Used to work smoothly, unfortunately, not anymore.

Edited by iilied
Link to comment
On 1/9/2021 at 5:09 PM, iilied said:

I am not getting a handshake from WireGuard client on macOS. Used to be able to connect no problem, is there a common issue occurring atm after the latest client update?

 

Edit: Regenerated keys and tried to reconnect, still same issue. Able to connect, no data, no handshake. No idea what to do next. Used to work smoothly, unfortunately, not anymore.

I had the same problem, didn't get a handshake from either my PC or my Android.
I don't remember why, but one day I decided to try another port in the the "local endpoint" and also my router port forwarding setting.
It just started to work.
I had earlier successfully used the default port, but one day it just stopped working. I went for a long time before I got to change the port, I used my router's OpenVPN instead. Weird.

Link to comment
  • 2 weeks later...

is it possible to activate the VPN only when trying to access specific dns names oder ip adresses?

 

scenario : on the road , logged into 5G , no VPN -> open my SecurityCam app which points to 192.x.x.x , VPN will start and shutdown when app is closed (or specific idle time)

 

or connect only when i try to connect to a specific ip range would be great

Edited by reppmic
update text
Link to comment
2 hours ago, reppmic said:

is it possible to activate the VPN only when trying to access specific dns names oder ip adresses?

 

scenario : on the road , logged into 5G , no VPN -> open my SecurityCam app which points to 192.x.x.x , VPN will start and shutdown when app is closed (or specific idle time)

 

or connect only when i try to connect to a specific ip range would be great

The Wireguard app on your phone has nothing to do with Wireguard running on Unraid.  You'd need to address this issue to the developer of the Wireguard app.

Link to comment
49 minutes ago, Energen said:

The Wireguard app on your phone has nothing to do with Wireguard running on Unraid.  You'd need to address this issue to the developer of the Wireguard app.

 

ok, thanks for clearify , but is it also not possible to setup unraid Wireguard that the incoming client can only access a specific ip range?

Link to comment
14 hours ago, reppmic said:

 

ok, thanks for clearify , but is it also not possible to setup unraid Wireguard that the incoming client can only access a specific ip range?

You can do this by specifying the IP range allowed when defining a tunnel at the Unraid end.

 

a point to note is that if you want to access the IPs on your local LAN form a remote point across a WireGuard link then the client must be on a different subnet to that used on your home LAN.   This may well mean that you want to avoid using commonly used subsets like 192.168.0.x and 192.168.1.x on your home LAN as you will find there is a high chance of the client being on one of these subnets.

  • Thanks 1
Link to comment

BUG found,

I have two wg interfaces wg0 and wg1

wg0 is set to no server NAT, thus thus no associated firewall rules are set on pre-up and post-down

wg1 is set to enable server NAT

After unraid reboots

wg1 will fail to start due to non existent WIREGUARD chain in iptables.

I have to manually add WIREGUARD chain to start the wg1 interface.

Link to comment
On 1/11/2021 at 7:52 PM, ICDeadPpl said:

I had the same problem, didn't get a handshake from either my PC or my Android.
I don't remember why, but one day I decided to try another port in the the "local endpoint" and also my router port forwarding setting.
It just started to work.
I had earlier successfully used the default port, but one day it just stopped working. I went for a long time before I got to change the port, I used my router's OpenVPN instead. Weird.

tried this, unfortunately didn’t work. don’t know where to start to solve this.

Link to comment

This outright does not work for me. I followed everything in the tutorial, the correct port is forwarded and the correct public keys are on my phone, but whenever I connect to the VPN I set up on Wireguard, the internet just stops working.

 

Here is the log:

 

https://ghostbin.co/paste/b9hxm

 

--------- beginning of main
01-27 05:11:03.732  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:03.759  9254  9254 D NetworkSecurityConfig: No Network Security Config specified, using platform default
01-27 05:11:03.760  9254  9254 D NetworkSecurityConfig: No Network Security Config specified, using platform default
01-27 05:11:03.766  9254  9254 I WireGuard/Application: WireGuard/1.0.20201224 (Android 30; arm64-v8a; sdm845; Phone; Phone:user/release-keys)
01-27 05:11:03.774  9254  9254 W reguard.androi: Accessing hidden field Ljava/util/Collections$SynchronizedCollection;->mutex:Ljava/lang/Object; (greylist-max-o, reflection, denied)
01-27 05:11:03.774  9254  9254 W reguard.androi: Accessing hidden method Ljava/util/Collections$SynchronizedSet;-><init>(Ljava/util/Set;Ljava/lang/Object;)V (greylist-max-o, reflection, denied)
01-27 05:11:03.774  9254  9254 W reguard.androi: Accessing hidden method Ljava/util/Collections$SynchronizedCollection;-><init>(Ljava/util/Collection;Ljava/lang/Object;)V (greylist-max-o, reflection, denied)
01-27 05:11:03.784  9254  9276 W WireGuard/RootShell: Root check did not return correct UID: null
--------- beginning of events
01-27 05:11:03.791  9254  9254 I wm_on_create_called: [190980701,com.wireguard.android.activity.MainActivity,performCreate]
01-27 05:11:03.798  9254  9254 I wm_on_start_called: [190980701,com.wireguard.android.activity.MainActivity,handleStartActivity]
01-27 05:11:03.799  9254  9254 I wm_on_resume_called: [190980701,com.wireguard.android.activity.MainActivity,RESUME_ACTIVITY]
01-27 05:11:03.805  9254  9254 I wm_on_top_resumed_gained_called: [190980701,com.wireguard.android.activity.MainActivity,topStateChangedWhenResumed]
01-27 05:11:03.813  9254  9279 I AdrenoGLES: QUALCOMM build                   : 35556ba, I9ca166462c
01-27 05:11:03.813  9254  9279 I AdrenoGLES: Build Date                       : 08/07/19
01-27 05:11:03.813  9254  9279 I AdrenoGLES: OpenGL ES Shader Compiler Version: EV031.27.02.00
01-27 05:11:03.813  9254  9279 I AdrenoGLES: Local Branch                     : 
01-27 05:11:03.813  9254  9279 I AdrenoGLES: Remote Branch                    : 
01-27 05:11:03.813  9254  9279 I AdrenoGLES: Remote Branch                    : 
01-27 05:11:03.813  9254  9279 I AdrenoGLES: Reconstruct Branch               : 
01-27 05:11:03.813  9254  9279 I AdrenoGLES: Build Config                     : S P 8.0.8 AArch64
01-27 05:11:03.816  9254  9279 I AdrenoGLES: PFP: 0x016ee187, ME: 0x00000000
01-27 05:11:03.831  9254  9279 I Gralloc4: mapper 4.x is not supported
01-27 05:11:03.832  9254  9279 W Gralloc3: mapper 3.x is not supported
01-27 05:11:04.233  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:04.923  9254  9254 I menu_item_selected: [0,Settings]
01-27 05:11:04.928  9254  9254 I wm_on_top_resumed_lost_called: [190980701,com.wireguard.android.activity.MainActivity,topStateChangedWhenResumed]
01-27 05:11:04.928  9254  9254 I wm_on_paused_called: [190980701,com.wireguard.android.activity.MainActivity,performPause]
01-27 05:11:04.935  9254  9254 I wm_on_create_called: [21204620,com.wireguard.android.activity.SettingsActivity,performCreate]
01-27 05:11:04.948  9254  9254 I wm_on_start_called: [21204620,com.wireguard.android.activity.SettingsActivity,handleStartActivity]
01-27 05:11:04.948  9254  9254 I wm_on_resume_called: [21204620,com.wireguard.android.activity.SettingsActivity,RESUME_ACTIVITY]
01-27 05:11:04.952  9254  9254 I wm_on_top_resumed_gained_called: [21204620,com.wireguard.android.activity.SettingsActivity,topStateChangedWhenResumed]
01-27 05:11:04.956  9254  9296 W WireGuard/RootShell: Root check did not return correct UID: null
01-27 05:11:04.984  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:05.391  9254  9254 I wm_on_stop_called: [190980701,com.wireguard.android.activity.MainActivity,STOP_ACTIVITY_ITEM]
01-27 05:11:06.109  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:07.805  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:09.807  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:10.022  9254  9254 I wm_on_top_resumed_lost_called: [21204620,com.wireguard.android.activity.SettingsActivity,topStateChangedWhenResumed]
01-27 05:11:10.023  9254  9254 I wm_on_paused_called: [21204620,com.wireguard.android.activity.SettingsActivity,performPause]
01-27 05:11:10.035  9254  9254 I wm_on_create_called: [260129516,com.wireguard.android.activity.LogViewerActivity,performCreate]
01-27 05:11:10.036  9254  9254 I wm_on_start_called: [260129516,com.wireguard.android.activity.LogViewerActivity,handleStartActivity]
01-27 05:11:10.036  9254  9254 I wm_on_resume_called: [260129516,com.wireguard.android.activity.LogViewerActivity,RESUME_ACTIVITY]
01-27 05:11:10.039  9254  9254 I wm_on_top_resumed_gained_called: [260129516,com.wireguard.android.activity.LogViewerActivity,topStateChangedWhenResumed]
01-27 05:11:10.444  9254  9279 D OpenGLRenderer: endAllActiveAnimators on 0x774f772b00 (RippleDrawable) with handle 0x766f775e70
01-27 05:11:10.447  9254  9254 I wm_on_stop_called: [21204620,com.wireguard.android.activity.SettingsActivity,STOP_ACTIVITY_ITEM]
01-27 05:11:11.808  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:13.817  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:15.819  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:17.820  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:19.822  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:21.825  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:23.828  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:25.837  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:27.566  9254  9254 I wm_on_top_resumed_lost_called: [260129516,com.wireguard.android.activity.LogViewerActivity,topStateChangedWhenResumed]
01-27 05:11:27.574  9254  9254 I wm_on_paused_called: [260129516,com.wireguard.android.activity.LogViewerActivity,performPause]
01-27 05:11:27.590  9254  9254 I wm_on_restart_called: [21204620,com.wireguard.android.activity.SettingsActivity,performRestartActivity]
01-27 05:11:27.595  9254  9254 I wm_on_start_called: [21204620,com.wireguard.android.activity.SettingsActivity,handleStartActivity]
01-27 05:11:27.596  9254  9254 I wm_on_resume_called: [21204620,com.wireguard.android.activity.SettingsActivity,RESUME_ACTIVITY]
01-27 05:11:27.596  9254  9254 I wm_on_top_resumed_gained_called: [21204620,com.wireguard.android.activity.SettingsActivity,topWhenResuming]
01-27 05:11:27.844  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:28.084  9254  9254 I wm_on_stop_called: [260129516,com.wireguard.android.activity.LogViewerActivity,LIFECYCLER_STOP_ACTIVITY]
01-27 05:11:28.086  9254  9254 I wm_on_destroy_called: [260129516,com.wireguard.android.activity.LogViewerActivity,performDestroy]
01-27 05:11:29.852  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:31.686  9254  9254 I wm_on_top_resumed_lost_called: [21204620,com.wireguard.android.activity.SettingsActivity,topStateChangedWhenResumed]
01-27 05:11:31.688  9254  9254 I wm_on_paused_called: [21204620,com.wireguard.android.activity.SettingsActivity,performPause]
01-27 05:11:31.700  9254  9254 I wm_on_restart_called: [190980701,com.wireguard.android.activity.MainActivity,performRestartActivity]
01-27 05:11:31.703  9254  9254 I wm_on_start_called: [190980701,com.wireguard.android.activity.MainActivity,handleStartActivity]
01-27 05:11:31.703  9254  9254 I wm_on_resume_called: [190980701,com.wireguard.android.activity.MainActivity,RESUME_ACTIVITY]
01-27 05:11:31.703  9254  9254 I wm_on_top_resumed_gained_called: [190980701,com.wireguard.android.activity.MainActivity,topWhenResuming]
01-27 05:11:31.855  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:32.151  9254  9254 I wm_on_stop_called: [21204620,com.wireguard.android.activity.SettingsActivity,LIFECYCLER_STOP_ACTIVITY]
01-27 05:11:32.157  9254  9254 I wm_on_destroy_called: [21204620,com.wireguard.android.activity.SettingsActivity,performDestroy]
01-27 05:11:32.895  9254  9296 I WireGuard/GoBackend: Bringing tunnel orbivpn UP
01-27 05:11:32.896  9254  9296 D WireGuard/GoBackend: Requesting to start VpnService
01-27 05:11:33.095  9254  9296 D WireGuard/GoBackend: Go backend v0.0.20201118
01-27 05:11:33.096  9254  9296 D WireGuard/GoBackend/orbivpn: Debug log enabled
01-27 05:11:33.096  9254  9296 I WireGuard/GoBackend/orbivpn: Attaching to interface tun0
01-27 05:11:33.110  9254  9254 I auditd  : type=1400 audit(0.0:571): avc: denied { read } for comm="DefaultDispatch" name="somaxconn" dev="proc" ino=169316 scontext=u:r:untrusted_app:s0:c88,c257,c512,c768 tcontext=u:object_r:proc_net:s0 tclass=file permissive=0 app=com.wireguard.android
01-27 05:11:33.110  9254  9254 W DefaultDispatch: type=1400 audit(0.0:571): avc: denied { read } for name="somaxconn" dev="proc" ino=169316 scontext=u:r:untrusted_app:s0:c88,c257,c512,c768 tcontext=u:object_r:proc_net:s0 tclass=file permissive=0 app=com.wireguard.android
01-27 05:11:33.118  9254  9544 D WireGuard/GoBackend/orbivpn: Routine: handshake worker - started
01-27 05:11:33.118  9254  9293 D WireGuard/GoBackend/orbivpn: Routine: decryption worker - started
01-27 05:11:33.118  9254  9296 D WireGuard/GoBackend/orbivpn: UAPI: Updating private key
01-27 05:11:33.118  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: event worker - started
01-27 05:11:33.118  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: encryption worker - started
01-27 05:11:33.118  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: decryption worker - started
01-27 05:11:33.118  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: encryption worker - started
01-27 05:11:33.118  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: decryption worker - started
01-27 05:11:33.118  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: handshake worker - started
01-27 05:11:33.119  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: encryption worker - started
01-27 05:11:33.119  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: decryption worker - started
01-27 05:11:33.119  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: handshake worker - started
01-27 05:11:33.119  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: TUN reader - started
01-27 05:11:33.119  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: encryption worker - started
01-27 05:11:33.119  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: decryption worker - started
01-27 05:11:33.119  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: handshake worker - started
01-27 05:11:33.119  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: decryption worker - started
01-27 05:11:33.119  9254  9296 D WireGuard/GoBackend/orbivpn: UAPI: Removing all peers
01-27 05:11:33.119  9254  9296 D WireGuard/GoBackend/orbivpn: UAPI: Transition to peer configuration
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: encryption worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: handshake worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: encryption worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: decryption worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: handshake worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: encryption worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: encryption worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: decryption worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: handshake worker - started
01-27 05:11:33.119  9254  9542 D WireGuard/GoBackend/orbivpn: Routine: handshake worker - started
01-27 05:11:33.120  9254  9296 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - UAPI: Created
01-27 05:11:33.120  9254  9296 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - UAPI: Adding allowedip
01-27 05:11:33.120  9254  9296 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - UAPI: Updating endpoint
01-27 05:11:33.120  9254  9296 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - UAPI: Updating preshared key
01-27 05:11:33.126  9254  9296 D WireGuard/GoBackend/orbivpn: UDP bind has been updated
01-27 05:11:33.126  9254  9296 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Starting...
01-27 05:11:33.126  9254  9545 D WireGuard/GoBackend/orbivpn: Routine: receive incoming IPv6 - started
01-27 05:11:33.126  9254  9296 I WireGuard/GoBackend/orbivpn: Device started
01-27 05:11:33.126  9254  9289 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Routine: nonce worker - started
01-27 05:11:33.126  9254  9289 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Routine: sequential sender - started
01-27 05:11:33.126  9254  9289 D WireGuard/GoBackend/orbivpn: Routine: receive incoming IPv4 - started
01-27 05:11:33.127  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Routine: sequential receiver - started
01-27 05:11:33.316  9254  9289 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:11:33.319  9254  9289 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Awaiting keypair
01-27 05:11:33.867  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:35.875  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:36.327  9254  9254 I menu_item_selected: [0,Settings]
01-27 05:11:36.338  9254  9254 I wm_on_top_resumed_lost_called: [190980701,com.wireguard.android.activity.MainActivity,topStateChangedWhenResumed]
01-27 05:11:36.338  9254  9254 I wm_on_paused_called: [190980701,com.wireguard.android.activity.MainActivity,performPause]
01-27 05:11:36.345  9254  9254 I wm_on_create_called: [95584283,com.wireguard.android.activity.SettingsActivity,performCreate]
01-27 05:11:36.353  9254  9254 I wm_on_start_called: [95584283,com.wireguard.android.activity.SettingsActivity,handleStartActivity]
01-27 05:11:36.354  9254  9254 I wm_on_resume_called: [95584283,com.wireguard.android.activity.SettingsActivity,RESUME_ACTIVITY]
01-27 05:11:36.357  9254  9254 I wm_on_top_resumed_gained_called: [95584283,com.wireguard.android.activity.SettingsActivity,topStateChangedWhenResumed]
01-27 05:11:36.363  9254  9296 W WireGuard/RootShell: Root check did not return correct UID: null
01-27 05:11:36.775  9254  9279 D OpenGLRenderer: endAllActiveAnimators on 0x774f764670 (RippleDrawable) with handle 0x766f778d20
01-27 05:11:36.779  9254  9254 I wm_on_stop_called: [190980701,com.wireguard.android.activity.MainActivity,STOP_ACTIVITY_ITEM]
01-27 05:11:37.663  9254  9254 I wm_on_top_resumed_lost_called: [95584283,com.wireguard.android.activity.SettingsActivity,topStateChangedWhenResumed]
01-27 05:11:37.664  9254  9254 I wm_on_paused_called: [95584283,com.wireguard.android.activity.SettingsActivity,performPause]
01-27 05:11:37.674  9254  9254 I wm_on_create_called: [214810710,com.wireguard.android.activity.LogViewerActivity,performCreate]
01-27 05:11:37.675  9254  9254 I wm_on_start_called: [214810710,com.wireguard.android.activity.LogViewerActivity,handleStartActivity]
01-27 05:11:37.676  9254  9254 I wm_on_resume_called: [214810710,com.wireguard.android.activity.LogViewerActivity,RESUME_ACTIVITY]
01-27 05:11:37.678  9254  9254 I wm_on_top_resumed_gained_called: [214810710,com.wireguard.android.activity.LogViewerActivity,topStateChangedWhenResumed]
01-27 05:11:37.876  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:38.128  9254  9254 I wm_on_stop_called: [95584283,com.wireguard.android.activity.SettingsActivity,STOP_ACTIVITY_ITEM]
01-27 05:11:38.588  9254  9289 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:11:38.588  9254  9289 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:11:39.877  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:41.879  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:43.753  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:11:43.753  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:11:43.882  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:45.884  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:47.886  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:49.037  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:11:49.037  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:11:49.867  9254  9254 I wm_on_top_resumed_lost_called: [214810710,com.wireguard.android.activity.LogViewerActivity,topStateChangedWhenResumed]
01-27 05:11:49.879  9254  9254 I wm_on_paused_called: [214810710,com.wireguard.android.activity.LogViewerActivity,performPause]
01-27 05:11:49.888  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:49.916  9254  9254 I wm_on_stop_called: [214810710,com.wireguard.android.activity.LogViewerActivity,STOP_ACTIVITY_ITEM]
01-27 05:11:51.889  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:53.902  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:54.216  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:11:54.216  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:11:55.916  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:57.918  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:11:59.411  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:11:59.923  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:01.931  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:03.940  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:04.654  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:05.298  9254  9254 I wm_on_restart_called: [214810710,com.wireguard.android.activity.LogViewerActivity,performRestartActivity]
01-27 05:12:05.298  9254  9254 I wm_on_start_called: [214810710,com.wireguard.android.activity.LogViewerActivity,handleStartActivity]
01-27 05:12:05.298  9254  9254 I wm_on_resume_called: [214810710,com.wireguard.android.activity.LogViewerActivity,RESUME_ACTIVITY]
01-27 05:12:05.298  9254  9254 I wm_on_top_resumed_gained_called: [214810710,com.wireguard.android.activity.LogViewerActivity,topWhenResuming]
01-27 05:12:05.941  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:07.944  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:09.736  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:12:09.738  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:09.946  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:11.949  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:13.758  9254  9254 I menu_item_selected: [0,Export log file]
01-27 05:12:13.951  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:14.897  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:15.954  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:17.956  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:19.957  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:20.044  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:12:20.044  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:20.387  9254  9254 I wm_on_top_resumed_lost_called: [214810710,com.wireguard.android.activity.LogViewerActivity,topStateChangedWhenResumed]
01-27 05:12:20.395  9254  9254 I wm_on_paused_called: [214810710,com.wireguard.android.activity.LogViewerActivity,performPause]
01-27 05:12:20.422  9254  9254 I wm_on_stop_called: [214810710,com.wireguard.android.activity.LogViewerActivity,STOP_ACTIVITY_ITEM]
01-27 05:12:21.958  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:23.965  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:25.187  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:12:25.187  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:25.970  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:27.975  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:29.978  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:30.487  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 3)
01-27 05:12:30.487  9254  9545 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:31.982  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:33.983  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:35.754  9254  9289 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:12:35.755  9254  9289 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:35.988  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:37.991  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:39.995  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:40.836  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:12:40.836  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:42.002  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:44.003  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:44.966  9254  9254 I wm_on_restart_called: [214810710,com.wireguard.android.activity.LogViewerActivity,performRestartActivity]
01-27 05:12:44.966  9254  9254 I wm_on_start_called: [214810710,com.wireguard.android.activity.LogViewerActivity,handleStartActivity]
01-27 05:12:44.966  9254  9254 I wm_on_resume_called: [214810710,com.wireguard.android.activity.LogViewerActivity,RESUME_ACTIVITY]
01-27 05:12:44.966  9254  9254 I wm_on_top_resumed_gained_called: [214810710,com.wireguard.android.activity.LogViewerActivity,topWhenResuming]
01-27 05:12:45.950  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Handshake did not complete after 5 seconds, retrying (try 2)
01-27 05:12:45.950  9254  9542 D WireGuard/GoBackend/orbivpn: peer(WEGn…VgQY) - Sending handshake initiation
01-27 05:12:46.003  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:48.005  9254  9266 E reguard.androi: failed to connect to jdwp control socket: Connection refused
01-27 05:12:49.188  9254  9254 I menu_item_selected: [0,Export log file]

 

Edited by Stubbs
Link to comment

Hi, i installed wireguard this week , all works fine but i noticed one thing:

 

even when i deactivate Wireguard or/and the open UDP Port on my router iOS „established“ a VPN connection (which is not working) but it shows „connected“ and the VPN Sign is in the upper right corner.

 

any ideas why?

 

greetings

Link to comment
On 1/9/2021 at 10:09 AM, iilied said:

I am not getting a handshake from WireGuard client on macOS. Used to be able to connect no problem, is there a common issue occurring atm after the latest client update?

 

Edit: Regenerated keys and tried to reconnect, still same issue. Able to connect, no data, no handshake. No idea what to do next. Used to work smoothly, unfortunately, not anymore.

I am having this same issue. I have looked at 3 different install guides and they all take the same steps to set this up. Yet I have the issue with not getting a handshake. It seems a few people are having this issue. not sure why there isn't a clear fix for such a common issue. 

 

For me I'm testing on windows 10 and android. Client log just keeps sending handshake and unraid never shows handshake arriving. 

Link to comment

i've had trouble getting wireguard on unraid to work right. i can connect. but thats it. no access to anything. running  a wireguard vm works. i can't get any combination to work with this unraid plugin. i've used this configurator tool to setup wireguard in pfsense-devel and vm. https://www.wireguardconfig.com/

while unraid allows conf importing none of what this well used site generates can be imported correctly. importing what this website spits out into wireguard vm, or pfsense-devel works and connection link is instant. i'm sure i can't make dynamix wireguard to work from some unknown reason i can't seem to trouble shoot.

Edited by letrain
Link to comment

Hey Folks,

i am currently running into a problem and i cant see the solution.

 

Setup: 

router (192.168.1.1)

dns hosted on a raspberry pihole (192.168.1.2)

unraid (192.168.1.3) (with bridged, host dockers and dockers running on br0)

 

I got wireguard up and running and put my raspberry as DNS into the Wireguardconfig. 

Now i have the Problem that i cannot access the dockers that are running on br0. 

I think that my error is in the static route. I've set that on my router that 10.253.0.0/24 with gateway 192.168.1.3 but for some reason i still cannot access it. Can anyone help me out?

 

Thanks!

 

Link to comment
On 11/9/2020 at 6:32 PM, Guns McWar said:

Just posting an issue (and solution) I ran into today. I haven't read through all 16 pages of this thread to see if anyone else has experienced this, so I apologize if this has been covered before.

 

If my peer name has an ampersand (&) in it, my connection does not work. After removing the ampersand, my connection immediately started working again (using both the macOS and Android WireGuard clients).

 

Hopefully this helps someone else who might be pulling their hair out while wondering why their VPN connection stopped/never worked.

 

I am looking for ways to improve the WireGuard interface so we can avoid configuration issues. I was prepared to add a check for ampersands in the peer name, but in my testing it doesn't seem to cause any problems.

 

I am using the official WireGuard Android client (dated Dec 24, 2020). Would you mind testing this again? I don't want to prevent people from using ampersands unnecessarily 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.