@@kristoffersyversen3474i saved this script : #!/bin/sh -e modprobe tun //load tun and dependencies at this path : /usr/local/etc/init.d/tun.sh and chmod 0755 Let me know if that works for you :)
I followed your instructions to the letter and in my logs I see "Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)". lsmod command shows that the interfaces needed are present for the container
Weird, I've tested the 3 methods and they've worked for me. I would say, make the container have highest privileges just in case. Restart the NAS after applying through SSH (the most invasive but more likely to work way).
Hi@@gabrielb86ve, you do that when creating or editing the container. There is an option there that says High Privileges. In an enterprise environment it is a worry but if your NAS is not exposed to the internet and is only accessible in your local network, I would say you don't have to worry much.
@@mateuszkaflowski3827 Check that you followed the steps properly. If you used any of the automated fix methods, it should just work. If you followed the manual way, then yes, you have to connect to the VPN manually when you restart and then restart the container.
This video is a guide for Synology users. It must be the same thing. You need to create the tunnel interface. However, I don't know the commands that you need to run in Ubuntu.
![Can we run Gluetun in Docker in a Synology NAS [Video Request]](http://i.ytimg.com/vi/Mt7tlnneV38/mqdefault.jpg)
You definitely got it, thanks ! I had been looking for an answer for this error in my QBiT VPN container
thanks a lot ! managed to tweak it a bit for asustor and solved my issue !
Awesome!
want to share how you did it? :D
@@kristoffersyversen3474i saved this script :
#!/bin/sh -e
modprobe tun //load tun and dependencies
at this path : /usr/local/etc/init.d/tun.sh
and chmod 0755
Let me know if that works for you :)
You are my MAN! Thank you. You are a lifesaver.
YES!! Your're my man, too :-)
I followed your instructions to the letter and in my logs I see "Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)".
lsmod command shows that the interfaces needed are present for the container
Weird, I've tested the 3 methods and they've worked for me. I would say, make the container have highest privileges just in case. Restart the NAS after applying through SSH (the most invasive but more likely to work way).
@@techbytetips Bro, that worked. For anyone else:
Tick the box under 'Capabilities' "Execute container using high privilege'.
Thanks again.
Cant find your reference guide. I am a noob, can I have the link please
github.com/Tech-Byte-Tips/Reference-Guides/blob/main/Fix-Synology-VPN-Dev-Tun-Issue.md
I'll put the link in the description.
hey im still getting the /dev/net/tun (TUN/TAP) error but i followed all the steps, any tips?
You have to also give the container highest privileges in Synology, unfortunately.
@@techbytetips Hey, thanks for the video. How do I give the container the highest privileges? And how risky would that be?
Hi@@gabrielb86ve, you do that when creating or editing the container. There is an option there that says High Privileges. In an enterprise environment it is a worry but if your NAS is not exposed to the internet and is only accessible in your local network, I would say you don't have to worry much.
@@techbytetips Even with high privileges I get the error afer restarting NAS and need to stop and start container. Why?
@@mateuszkaflowski3827 Check that you followed the steps properly.
If you used any of the automated fix methods, it should just work.
If you followed the manual way, then yes, you have to connect to the VPN manually when you restart and then restart the container.
I am using ubuntu i am trying to connect to my vpn using open vpn i get this you must define tun/tap device (--dev )
This video is a guide for Synology users. It must be the same thing. You need to create the tunnel interface. However, I don't know the commands that you need to run in Ubuntu.