Im still trying to get it running on the NAS.
The network interface is enp3s0 on OMV interface
Im still trying to get it running on the NAS.
The network interface is enp3s0 on OMV interface
Did you insert the name of the interface in the beginning of the script?
hmmm no, although I can see that in the instructions. Will give it a go
Tried changing eth0 to enp3s0 but it didn't help
You might now have old Data drin your first try.
Check your wireguard config Files or delete them before that Second try.
Is the Error exactly the Same?
I went into /etc/wireguard and deleting all the files in there. Ran the script again and it had the same error
Ok so I removed all of the WG packages, did update and upgrade, rebooted, and finally the script ran until the end!
I have forwarded the port on my router and the iOS client connects via the QR code although I can't get any internet or local traffic while connected.
Slowly getting there...
What is the output when you type wg on your server.
Also on your iOS what is specified for AllowedIPs (should be 0.0.0.0/0)?
public key: xxxxxxxxxx
private key: (hidden)
listening port 51820
peer: xxxxxxxxxx
allowed ips: 192.168.1.0/24
I have xxx'd out the long strings as I'm not sure if I should be posting them.
On iOS the Allowed IPs says: 0.0.0.0/0
QuoteI have xxx'd out the long strings as I'm not sure if I should be posting them.
That's fine.
When you type wg and the connection to your phone works it should have a line which says latest handshake x min x sec
I tried with the Mac client, same result. It says its connected but nothing passes though. No difference when I run wg as well.
I'm beginning to think it may be my shitty isp router. I had a IPsec VPN docker working for ages but one day all my devices stopped sending data even though they were connected, all except my android phone for some strange reason. Its the only reason I have been looking for another option.
In any case here is the log from the Mac.
2019-11-03 11:58:14.825958: [APP] App version: 0.0.20191012 (14); Go backend version: 0.0.20190909
2019-11-03 12:00:06.049070: [APP] startActivation: Entering (tunnel: Office WG)
2019-11-03 12:00:06.053677: [APP] startActivation: Starting tunnel
2019-11-03 12:00:06.054392: [APP] startActivation: Success
2019-11-03 12:00:06.063820: [APP] Tunnel 'Office WG' connection status changed to 'connecting'
2019-11-03 12:00:06.551000: [NET] App version: 0.0.20191012 (14); Go backend version: 0.0.20190909
2019-11-03 12:00:06.551307: [NET] Starting tunnel from the app
2019-11-03 12:00:11.054034: [APP] Status update notification timeout for tunnel 'Office WG'. Tunnel status is now 'connecting'.
2019-11-03 12:00:11.599368: [NET] Tunnel interface is utun1
2019-11-03 12:00:11.600350: [NET] Attaching to interface
2019-11-03 12:00:11.601639: [NET] Routine: handshake worker - started
2019-11-03 12:00:11.601810: [NET] Routine: decryption worker - started
2019-11-03 12:00:11.601944: [NET] Routine: handshake worker - started
2019-11-03 12:00:11.602051: [NET] Routine: encryption worker - started
2019-11-03 12:00:11.602159: [NET] Routine: decryption worker - started
2019-11-03 12:00:11.602277: [NET] Routine: handshake worker - started
2019-11-03 12:00:11.602390: [NET] Routine: event worker - started
2019-11-03 12:00:11.602494: [NET] Routine: encryption worker - started
2019-11-03 12:00:11.602604: [NET] Routine: encryption worker - started
2019-11-03 12:00:11.602717: [NET] Routine: decryption worker - started
2019-11-03 12:00:11.602825: [NET] Routine: handshake worker - started
2019-11-03 12:00:11.602930: [NET] Routine: encryption worker - started
2019-11-03 12:00:11.603046: [NET] Routine: encryption worker - started
2019-11-03 12:00:11.603148: [NET] Routine: encryption worker - started
2019-11-03 12:00:11.603254: [NET] Routine: decryption worker - started
2019-11-03 12:00:11.603363: [NET] Routine: handshake worker - started
2019-11-03 12:00:11.603476: [NET] Routine: decryption worker - started
2019-11-03 12:00:11.603586: [NET] Routine: encryption worker - started
2019-11-03 12:00:11.603698: [NET] Routine: encryption worker - started
2019-11-03 12:00:11.603809: [NET] Routine: handshake worker - started
2019-11-03 12:00:11.603915: [NET] Routine: decryption worker - started
2019-11-03 12:00:11.604023: [NET] Routine: TUN reader - started
2019-11-03 12:00:11.604169: [NET] Routine: decryption worker - started
2019-11-03 12:00:11.604236: [NET] Routine: decryption worker - started
2019-11-03 12:00:11.604342: [NET] Routine: handshake worker - started
2019-11-03 12:00:11.604456: [NET] Routine: handshake worker - started
2019-11-03 12:00:11.604767: [NET] UAPI: Updating private key
2019-11-03 12:00:11.605084: [NET] UAPI: Updating listen port
2019-11-03 12:00:11.605175: [NET] UAPI: Removing all peers
2019-11-03 12:00:11.605289: [NET] UAPI: Transition to peer configuration
2019-11-03 12:00:11.605875: [NET] peer(Z5QE…YyTg) - UAPI: Created
2019-11-03 12:00:11.605999: [NET] peer(Z5QE…YyTg) - UAPI: Updating persistent keepalive interval
2019-11-03 12:00:11.606062: [NET] peer(Z5QE…YyTg) - UAPI: Removing all allowedips
2019-11-03 12:00:11.606172: [NET] peer(Z5QE…YyTg) - UAPI: Adding allowedip
2019-11-03 12:00:11.607060: [NET] Routine: receive incoming IPv6 - started
2019-11-03 12:00:11.607186: [NET] Routine: receive incoming IPv4 - started
2019-11-03 12:00:11.607315: [NET] UDP bind has been updated
2019-11-03 12:00:11.607400: [NET] peer(Z5QE…YyTg) - Starting...
2019-11-03 12:00:11.607673: [NET] peer(Z5QE…YyTg) - Routine: sequential sender - started
2019-11-03 12:00:11.607747: [NET] peer(Z5QE…YyTg) - Routine: nonce worker - started
2019-11-03 12:00:11.607854: [NET] peer(Z5QE…YyTg) - Routine: sequential receiver - started
2019-11-03 12:00:11.607999: [NET] Device started
2019-11-03 12:00:11.609593: [APP] Tunnel 'Office WG' connection status changed to 'connected'
2019-11-03 12:00:16.054947: [APP] Status update notification timeout for tunnel 'Office WG'. Tunnel status is now 'connected'.
2019-11-03 12:00:16.526069: [NET] peer(Z5QE…YyTg) - Sending handshake initiation
2019-11-03 12:00:16.527260: [NET] peer(Z5QE…YyTg) - Failed to send handshake initiation no known endpoint for peer
2019-11-03 12:00:16.527462: [NET] peer(Z5QE…YyTg) - Awaiting keypair
2019-11-03 12:00:21.801177: [NET] peer(Z5QE…YyTg) - Handshake did not complete after 5 seconds, retrying (try 2)
2019-11-03 12:00:21.801374: [NET] peer(Z5QE…YyTg) - Sending handshake initiation
2019-11-03 12:00:21.807963: [NET] peer(Z5QE…YyTg) - Failed to send handshake initiation no known endpoint for peer
2019-11-03 12:00:26.972475: [NET] peer(Z5QE…YyTg) - Handshake did not complete after 5 seconds, retrying (try 2)
2019-11-03 12:00:26.972710: [NET] peer(Z5QE…YyTg) - Sending handshake initiation
2019-11-03 12:00:26.979475: [NET] peer(Z5QE…YyTg) - Failed to send handshake initiation no known endpoint for peer
2019-11-03 12:00:32.260704: [NET] peer(Z5QE…YyTg) - Handshake did not complete after 5 seconds, retrying (try 2)
2019-11-03 12:00:32.261006: [NET] peer(Z5QE…YyTg) - Sending handshake initiation
2019-11-03 12:00:32.261464: [NET] peer(Z5QE…YyTg) - Failed to send handshake initiation no known endpoint for peer
2019-11-03 12:00:37.438737: [NET] peer(Z5QE…YyTg) - Handshake did not complete after 5 seconds, retrying (try 2)
2019-11-03 12:00:37.438898: [NET] peer(Z5QE…YyTg) - Sending handshake initiation
2019-11-03 12:00:37.439207: [NET] peer(Z5QE…YyTg) - Failed to send handshake initiation no known endpoint for peer
2019-11-03 12:00:42.691229: [NET] peer(Z5QE…YyTg) - Handshake did not complete after 5 seconds, retrying (try 2)
2019-11-03 12:00:42.691507: [NET] peer(Z5QE…YyTg) - Sending handshake initiation
2019-11-03 12:00:42.698144: [NET] peer(Z5QE…YyTg) - Failed to send handshake initiation no known endpoint for peer
2019-11-03 12:00:48.023410: [NET] peer(Z5QE…YyTg) - Handshake did not complete after 5 seconds, retrying (try 3)
2019-11-03 12:00:48.023634: [NET] peer(Z5QE…YyTg) - Sending handshake initiation
2019-11-03 12:00:48.030391: [NET] peer(Z5QE…YyTg) - Failed to send handshake initiation no known endpoint for peer
Display More
Quoteno known endpoint for peer
Is there an Endpoint specified under Peer in the conf of your iOS machine? Should be the external of your router or a dyndns address + the port (e.g. my.domain.com:51820)
Got this reply with an email but its not in the forum
---------------------------------
Zitat: „no known endpoint for peer
“
Is there an Endpoint specified under Peer in the conf of your iOS machine? Should be the external of your router or a dyndns address + the port (e.g. http://my.domain.com:51820)
---------------------------------
I added xx.xx.xx.xx:51820 to the iOS settings but it made no difference
Can you post the contents of your wgnet0.conf on both machines? You can obscure the sensitive parts.
I have been messing around with the IP addresses in the script, so this isn't the same a before, but it has the same outcome - I can connect fine but no data transfers
On OMV;
[Interface]
Address = 192.168.1.0/24 SaveConfig = true
ListenPort = 51820 PostUp = iptables -A FORWARD -i wgnet0 -j ACCEPT; iptables -A FORWARD -o $
PostDown = iptables -D FORWARD -i wgnet0 -j ACCEPT; iptables -D FORWARD -$
PrivateKey = APdxxx=
[Peer]
PublicKey = qlRxxx=
AllowedIPs = 192.168.1.0/24
On the iPad;
[Interface]
Public key = qlRxxx=
Addresses = 192.168.1.0/24
[Peer]
Public Key = LB9xxx=
Allowed IPs = 0.0.0.0/0
The IP configs look incorrect cause now both machines have the same IP. Try these confs. I reverted the IP adresses, cause they worked for me without changing them. To understand the workings of Wireguard I also suggest reading the main introduction on wireguard.com
[Interface]
Address = 10.192.122.1/24
SaveConfig = true
ListenPort = 51820
PostUp = iptables -A FORWARD -i wgnet0 -j ACCEPT; iptables -A FORWARD -o $
PostDown = iptables -D FORWARD -i wgnet0 -j ACCEPT; iptables -D FORWARD -$
PrivateKey = APdxxx=
[Peer]
PublicKey = qlRxxx=
AllowedIPs = 10.192.122.2/24
Display More
and on the iPad:
Unfortunately no luck with that.
Thanks for your help with this but I am going to give PiVPN a go. I will also see if I can somehow replace my router, this is the 3rd VPN that I cant get to work, so surely it must be a router problem or a problem with my system...
Is there a recommended was to uninstall everything?
So I really like Wireguard as I have used it on my Unraid server where it is implemented beautifuly and performs really well.
I tried the script but couldn't get it to work, I get the same errors as @aykaydub.
At first I also didn't set my network device.
Then I uninstalled everything like this (don't know if correct):
Then I run the script again with the correct network device, but I still couldn't get the script to finish...
I also tried @ryecoaarons plugin but this says there are unmet dependencies.
Doesn't mention which but I figured it might be the wirguard-tools from @Morlans post.
I am running OMV5 on amd64 though...
So I tried uploading wireguard-tools_0.0.20190702-3_amd64.deb but it says its not matching the naming convention.
So I would be really happy for some advice
Edit:
Tried to install wireguard tools manually:
apt install /sharedfolders/data/wireguard-tools_0.0.20190702-3_amd64.deb
Then tried to install the plugin again, but still no luck...
Display MoreI also tried @ryecoaarons plugin but this says there are unmet dependencies.
Doesn't mention which but I figured it might be the wirguard-tools from @Morlans post.
I am running OMV5 on amd64 though...
So I tried uploading wireguard-tools_0.0.20190702-3_amd64.deb but it says its not matching the naming convention.
So I would be really happy for some advice
Edit:
Tried to install wireguard tools manually:
apt install /sharedfolders/data/wireguard-tools_0.0.20190702-3_amd64.deb
Then tried to install the plugin again, but still no luck...
How did you get the plugin? If you enabled the beta repo (has to be done from command line), then the dependencies are there. If not and you just downloaded the plugin .deb, you will need to download the wireguard .deb packages as well. Download wireguard, wireguard-tools, wireguard-dkms from https://bintray.com/openmediav…ugin-developers/usul-beta
Ok thanks is there a guide on how to enable the beta repo?
I guess it would be better doing it with the beta repo as it will automatically find new version when they release, right?
I first thought it was the testing repo but obviously not.
Don’t have an account yet? Register yourself now and be a part of our community!