Gianpaolo Racca
Cadet
- Joined
- Oct 6, 2016
- Messages
- 6
Hi everybody,
I'm new here and new to FreeNAS which I installed some days ago.
I need to set up an openvpn client on my NAS box to be able to access its web interface from my home based vpn network.
I managed to start the client manually, but I can't do it automatically on boot.
I learned how to make persistent changes in rc.conf (although it will be overwritten on system update, right?), but I'm stuck with the directory
/usr/local/etc/openvpn which gets lost over a reboot.
I read that usually you install openvpn in a jail, but this would prevent me to access the FreeNAS web interface, right? And I for sure don't want to expose my http port to the world to access FreeNAS remotely.
So, what can I do to make conf dir persistent?
I already have
openvpn_enable="YES"
and
openvpn_configfile="/etc/openvpn/blackbox.conf"
in my rc.conf, but the openvpn startup script always looks for file in /usr/local/etc/openvpn
Any help is really appreciated.
I'm new here and new to FreeNAS which I installed some days ago.
I need to set up an openvpn client on my NAS box to be able to access its web interface from my home based vpn network.
I managed to start the client manually, but I can't do it automatically on boot.
I learned how to make persistent changes in rc.conf (although it will be overwritten on system update, right?), but I'm stuck with the directory
/usr/local/etc/openvpn which gets lost over a reboot.
I read that usually you install openvpn in a jail, but this would prevent me to access the FreeNAS web interface, right? And I for sure don't want to expose my http port to the world to access FreeNAS remotely.
So, what can I do to make conf dir persistent?
I already have
openvpn_enable="YES"
and
openvpn_configfile="/etc/openvpn/blackbox.conf"
in my rc.conf, but the openvpn startup script always looks for file in /usr/local/etc/openvpn
Any help is really appreciated.