search

runfalk / synology-wireguard

WireGuard support for some Synology NAS drives
MIT License
945 stars 132 forks source link

Encountering error upon launching wg-quick up #4

Closed harmfulmushroom closed 5 years ago

harmfulmushroom commented 5 years ago

Using your directions I am successful in running everything on my diskstation until I hit this message trying to use wg-quick up:

/usr/local/bin/wg-quick: line 31: resolvconf: command not found

This seemed to be a big issue with various ubuntu images, but unlike them I cannot run their fix sudo apt-get install resolvconf.

My unit is a DS1019+, I used your pre-configured apollolake SPK as my platform should be compatible going off the table. Any idea's on how to resolve this?

runfalk commented 5 years ago

That's concerning. I didn't expect differences between the same architecture. Which DSM version are you using?

Maybe @Spass1966 or @ShagoY who have Apollolake can help you out

ShagoY commented 5 years ago

"resolvconf" is only used when using the DNS variable in the Wireguard configuration file. And since I don't use it... No problem :-D

harmfulmushroom commented 5 years ago

Very cool, yeah that does appear to be what differs between my config file and a few others I've been reviewing (not sure how I missed this until now). I'll play around with things on my end and see if I can't get it working, either by removing the DNS portion of my config or re-configuring the server to not specify a DNS. Thanks!

runfalk commented 5 years ago

Thank you @ShagoY.

Let me know if everything else works as expected @harmfulmushroom and I'll add you drive to the compatibility table.

harmfulmushroom commented 5 years ago

Sure thing @runfalk, I removed the DNS portion of my config file and all loaded successfully. I now see the new interface listed so I should be good to go now!

Can confirm DS1019+ is compatible.

runfalk commented 5 years ago

Great! I've updated the compatibility table.

I'll close this issue for now. resolveconf support might be something to look into later, but that will have to be a separate issue.

the-lazy-fox commented 4 years ago

Hello @harmfulmushroom How did you make it work without the DNS section? I'm using a wireguard configuration from my VPN provider and it's part of the config. Thanks!

runfalk commented 4 years ago

I think you should be able to leave it out. I think the consequence may be that the DNS requests do not go through your VPN provider. This means that someone may see which hosts you are connecting to, but not the traffic passed to them. Depending on your use case this may or may not be a problem.

the-lazy-fox commented 3 years ago

On my side, it doesn't work without the DNS. I can't ping anything.