My own DNS forwarder (Tunlr clone)

I was following some tutorial on how to setup a tunlr clone blindly and couldn’t get things working… put some thought into it and it’s working now (sort of).

The guide I’m following was DIY clone of Netflix Tunlr/Unblock-Us/UnoTelly on cheap US based VPS

Only difference was that I was using sniproxy 0.3.4 instead of 0.1.1. 0.3.6 doesn’t seem to use /etc/sniproxy.conf at all so I didn’t get it working.


I might update this page to include the updated instruction set on a later date.


— Ignore below —

OS: CentOS 6 x86_64

Provider:  shared 0.5GB RAM 1TB @ 1Gbps bandwidth


cd /tmp

#rpm -Uvh epel-release-7-2.noarch.rpm
#rm -rf epel-release-7-2.noarch.rpm
rpm -Uvh epel-release-6-8.noarch.rpm
rm -rf epel-release-6-8.noarch.rpm

yum update -y yum install openssl vim git wget curl bind-utils telnet -y 
yum groupinstall "Development Tools" -y 
yum install rpmbuild autoconf automake curl libev libev-devel pcre pcre-devel perl udns-devel -y 
yum install bind bind-chroot -y 

cd /var/named/chroot/etc/ 
cp /etc/named.* . 
vi named.conf 
#edit named.conf 
vi /var/named/chroot/etc/named/db.override 
#edit db.override 
vi /var/named/chroot/etc/zones.override 
#edit zones.override 
chown -hR named:named /var/named/ 
rndc-confgen -a -r /dev/urandom -t /var/named/chroot 
chkconfig named on 
service named start 

cd /opt 
#latest version doesn't seem to use sniproxy.conf
#git clone 
#get 0.3.4 instead
cd ./sniproxy 
./ && ./configure && make dist 
rpmbuild --define "_sourcedir `pwd`" -ba --nodeps redhat/sniproxy.spec 
yum install /root/rpmbuild/RPMS/x86_64/sniproxy-0.* -y 

#version 0.3.4 install only
vi /etc/sniproxy.conf

#### sniproxy.conf #####
# grep '^[^#]' /etc/sniproxy.conf
user daemon
pidfile /var/tmp/
listener 107.155.x.y 80 {
        proto http
listener 107.155.x.y 443 {
        proto tls
table {
        netflix\.com *
	speedtest\.net *
#### end sniproxy.conf ####

cp ./redhat/sniproxy.init /etc/init.d/sniproxy 
chmod +x /etc/init.d/sniproxy 
chkconfig sniproxy on 
service sniproxy start

Server transition complete

I’ve moved all the accounts I wanted over to the new system under (cheesy name I know). Under this system there’s a nice billing management that will help me log and ensure that there are no mixups all integrated in a professional looking environment.

I’ve purchased a new domain validated security certificate so that you shouldn’t get too many warnings, so you know your data is secure.

Forgive me for posting on a tablet.

Server/Services merging

Just merged most of my servers and domains that I’ve worked on. This way it’s easier to manage and I can start cleaning out the other servers.

Using a control panel to help in keeping things orderly as well.

[s]Will update with more information when I’ve finished the cleanup.[/s]


Essentially completed the merge over. Currently, wondering if I should get a small dedicated server though since it’ll provide better resources.

ESXi Server

This is just a mini work-log of how I got my ESXi server running for use at my home.

Hardware specs:
Motherboard: Jetway NF9G-QM77
CPU: Intel i5-3320M SR0MX 120
RAM: 2 x Corsair Vengeance CMSX8GX3M1A1600C10 8GB
HDD: Plextor PX-128M5M 128GB mSata
PSU: Seasonic 350W 1U PSU (doesn’t fit the case, but good enough)
Case: U-NAS 8-bay with USB 3.0 front module

Extra specs:
Realtek 4-port GigE daughter board
LSI 9650SE-12ML RAID Card (3ware 9650SE)
4x Seagate 3TB Drives
1x WD 3TB Green Drive

ESXi 5.5
Windows Server 2012 R2 Standard (NAS and DLNA server)
Pfsense (To be installed)

Initial incompatibilities:
Out-of-box I believe ESXi detected the Intel GigE NICs but only mounted one of them. It also didn’t detect the Realtek daughter-board nor the RAID card.

An aside: ESXi 5.1u1 seemed to get some of the functionality working for the Realtek nics.

Overall problems:
– Realtek ports not detected
– LSI Raid card not detected
– LSI Raid detected but no drives found
– 3TB showed as 750GB

Found out that the Realtek daughter-board needed the Realtek 8168 driver package from ESXi 5.1/5.0, the LSI 9650SE also is an async driver which means I have to load it into the ISO or afterwards as well.  After creating a new ISO including the new Realtek drivers and the LSI raid driver, I managed to get the NICs working but the RAID card wasn’t detected still… Actually, the RAID card was shipped and I figured maybe the battery was dead or something wasn’t letting it detect properly. After 24 hours of letting it sit in the desktop with the power cord connected (still off) it was detected but didn’t load anything properly (no drives). After some tinkering I managed to get the RAID drivers loaded, had to load a newer aacraid driver in addition to the LSI drivers.

Later I found out, that the drives weren’t being detected properly as they showed as 746GB drives. I thought it was weird so I put in a WD 3TB drive that was known for sure to be compatible (although I found someone using the Seagates), but it was the same.  I realized I had misread the firmware number and I had one just before the 2TB+ compatibility, so I had to update the firmware to FE9X to work. All detected A-OK.


Beginning to end in a summed up form would be….

Driver list:

Installing ESXi 5.5 with drivers
1) Download the drivers to load (Realtek 8168, LSI 9650SE async, aacraid)
2) One-by-one load them into the ISO using ESXi Customizer (I believe I loaded the vib files but I’ve included the offline zips as well)
3) Create a USB using rufus
4) Install to the server
5) Configure network access to connected NIC
6) Log into ESXi server on remote machine
7) Setup and install a guest OS

Configure RAID card
1) Ensure firmware (FE9X is what I used) or higher is installed on the RAID card
2) Create your array, or configure single drives to use windows to create an array
* Note: there are two ways to configure the array, one is through the RAID cards bootloader but you need to be in BIOS mode  the other way is through the 3DM2 interface.

Configure windows
1) Install RAID Drivers, ensure the latest 3DM2 is installed to work with Windows 2012 R2
2) Setup RAID using Disk Manager (for Software RAID) or 3DM2 (for Hardware RAID)
3) Configure file server (initialize the disk)