Setup FreeNAS via VPN
FreeNas is a popular, free software program that you can find online. If you frequently download files through BitTorrent or Usenet then FreeNas is software which you might want to have. This type of app, however, makes you vulnerable in many ways. In this article, we will show you how to make a setup which is anonymous and truly secure with a network-attached server.
This post explains to you the procedure of creating a streaming and torrenting device with network support. In addition, we will show you a way through which you can set up Usenet and media managing tools for the purpose of downloading.
These detailed instructions for creating a NAS will basically allow you to be hidden from monitoring applications. We will take you through the steps you need to follow by using a top Virtual Private Network provider to stay anonymous and safe from prying eyes. We will also show you ways to set up an observing system so you are able to see what is going on your server without having to be there physically.
Starting with FreeNAS
We will use Nas4Free in this activity. Nas4Free is the new name for FreeNas 8. In case you don’t have a manual for Nas4Free, you can use the FreeNas 7one because they are similar. If you do not have either of these manuals, just do a quick Google search to download one then follow it to set up your software. Our goal here is to explain to you a method of creating your Virtual Private Network and remote managing program.
Selecting A Premium Virtual Private Network Service
First of all, you will have to get a most-suitable VPN service. We prefer to use Hidemyass VPN because it is the best Virtual Private Network for this specific purpose.
Installing Virtual Private Network in FreeNAS Box:
The 1st step at this point is to set up a ‘jail’ on the network-attached server. This ‘jail’ will allow you to setup specific applications to your network-attached server drive; however, you will only require to utilize this if your FreeNAS is to be setup from a USB drive. Otherwise, you may just proceed and go to the second phase.
You have to SSH right into your network-attached server as a 1st step. In case you are working with OS X, remember to apply the “ssh – l root [NAS IP]” command. When you have signed in using your password, you will have to install temp folders and the usr,var on the hard disk; this allows you to install applications which do not come with your network-attached server. Attach the folders on the hard disk after you have created them.
Step two is to setup the OpenVPN in order to link with the Virtual Private Network service you have subscribed to-again, your VPN has to be suitable for this. Be sure to check out the version to ensure you are making use of the suitable FreeBSD version. Check whether or not you are working while using 64-bit network-attached server as well, because it will influence anything you type in the command box.
Now, to link the OpenVPN to your VPN, look for instruction from the guidebook; that will normally be accessible as a ZIP file along with a few other files like config files, certificates (.crt).
After modifying the configuration file open it by using a text editor and ensure that you are using your Virtual Private Network server. You should, as well, see to it that the .key and .crt files are renamed properly for the Virtual Private Network you are making use of.
Once this is done, you have to SSH into your network-attached server just as before and then rename configuration file to the openvpn.conf. After that, drag the file into the fresh drive folder you have recently made.
You can now initialize OpenVPN through the Command field in your network-attached server web program. Check out Log under Diagnostics to see if you are having something like this: Process Sequence Done. You may make sure by SSH-ing right into your network-attached server by attempting to ping a well-known internet site. If you are not receiving a reply, then your configuration file has to be launched again and examined for issues.
The last step is to create a firewall which only lets your Virtual Private Network connection to proceed through. This has to be done via the network-attached server web interface. It also has to include commands which permit traffic from the Virtual Private Network’s IP range to get into your recently built network-attached server. Make sure that the destination and source IPs match exactly what your Virtual Private Network uses.
Remote Monitoring along with Dynamic DNS
The last part of this entire procedure is about creating a Dynamic DNS to get remote access. You may look at a zero cost service, if you do not require enhanced features. That said, either of these options suffices for the outcomes we are seeking to gain. At this point the idea is that you need to make use of this service as a means to help you recall the domain titles, so that you don’t have to remember huge numbers of IP addresses.
Next, you will now have to create the Dynamic DNS on the network-attached server and your router. You will find this beneath ‘settings’ on your router and below ‘services’ on the network-attached server web interface, the same place you checked the included DNS services.
The 2nd action is to forward the slots that your Virtual Private Network has allocated to you, on your network-attached server. To take an example; if you wish to gain access to your Bit Torrent downloads via network, you can alter the WebGUI configurations on the network-attached server to include the IP which your Virtual Private Network has allocated you.
You obtain the IP address by following the same procedure you used to create the OpenVPN. Likewise, if you are making use of other internet services, then all those IPs have to be provided in the network-attached server settings too.
The last stage is all about testing if you can get to your downloaded files remotely. At this stage, you want to ensure that everything works properly. Congratulations! You are now all set to go with complete remote access, anonymity and security.