Sign inSign up

intersoftlab/iptables-auth

By intersoftlab

•Updated about 9 years ago

iptables-auth

Image
0

428

intersoftlab/iptables-auth repository overview

⁠netflix-proxy Build Status

Docker packaged smart DNS proxy to watch Netflix, Hulu[n2], HBO Now and others out of region using BIND and sniproxy[n1]. Works for blocked sites too, such as PornHub⁠.

This solution will only work with devices supporting Server Name Indication (SNI)[n7]. To test, open a web browser on the device you are planning to watch content and go to this⁠ site (https://sni.velox.ch/).

Update March/2016: IPv6 addresses of common hosting providers are now blocked in the same way as IPv4. Netflix could to be "tagging" accounts too, so if your account is tagged, the only device that will work out of region is the desktop web browser (i.e. Chrome)[n11]. Netflix and BBC iPlayer are also perfoming geo checks on their media hosts, so the relevant media domains are now proxied by default[n8]. Please note, that proxying media delivery could increase the bandwidth bill you get from your VPS provider. However, since most VPS providers offer 1TB per month inclusive with each server and most home ISPs don't offer anywhere near that amount, it should be a moot point in most situations.

If you feel all of this is too complicated, I don't blame you. If you want change, vote with your wallet by cancelling your Netflix subscription and/or sign the petition:

Please see the Wiki⁠ page(s) for some common troubleshooting ideas.

Unblocked Netflix? Great success! Vote⁠ now and see the results⁠.

⁠Supported Services

The following are supported out of the box, however adding additional services is trivial and is done by updating zones.override file and running docker restart bind:

  • Netflix
  • Hulu[n2]
  • HBO Now
  • Amazon Instant Video
  • Crackle
  • Pandora
  • Vudu
  • blinkbox
  • BBC iPlayer[n5]
  • NBC Sports and potentially many more⁠

⁠Instructions

The following paragraphs show how to get this solution up and running with a few different Cloud providers I've tried so far.

The following is based on a standard Ubuntu Docker image provided by DigitalOcean, but should in theory work on any Linux distribution with Docker pre-installed. Do not enable native IPv6 on the host.

  1. Head over to Digital Ocean⁠ to get $10 USD credit
  2. Create a Droplet in a location closest to you using Docker 1.x on Ubuntu 14.04 (find in under One-click Apps tab).
  3. Create a free tunnel broker⁠ account.
  4. Create a regular tunnel⁠.
  5. Set the IPv4 Endpoint to the Droplet IP, pick a tunnel server in a location closest to you and click Create Tunnel.
  6. SSH to your server and run ping6 netflix.com; if you get Network is unreachable proceed to the next step, otherwise remove native IPv6 first.
  7. Run: git clone https://github.com/ab77/netflix-proxy /opt/netflix-proxy && cd /opt/netflix-proxy && ./build.sh -u <tunnelbroker-username> -p <tunnelbroker-password>, making sure to specify your HE tunnel username and password correctly.
  8. Make sure to record the credentials for the netflix-proxy admin site.
  9. Set your DNS server to the IP given at the end of the script, then go to this⁠ site to make sure the same IP is displayed.
  10. Finally, enjoy Netflix and others out of region.
  11. Enjoy or raise a new issue⁠ if something doesn't work quite right (also #netflix-proxy on freenode⁠).
⁠Authorising Additional IPs

If you want to share your system with friends and family, you can authorise their home IP address(s) using the netflix-proxy admin site, located at http://<ipaddr>:8080/, where ipaddr is the public IP address of your VPS. Login using admin account with the password you recorded during the build, in step 6.

⁠Dynamic IPs

You can also use the netflix-proxy admin site to update your IP address, should your ISP assign you a new one (e.g. via DHCP). If your IP address does change, all HTTP/HTTPS requests will automatically be redirected to the admin site on port 8080. All DNS requests will be redirected to dnsmasq instance running on port 5353. You will most likely need to purge your browser and system DNS caches after this (e.g. ipconfig /flushdns and chrome://net-internals/#dns) and/or reboot the relevant devices. This mechanism should work on browsers, but will most likely cause errors on other devices, such as Apple TVs and smart TVs. If you Internet stops working all of a sudden, try loading a browser and going to netflix.com.

⁠Automatic IP Authorization

WARNING: do not do enable this unless you know what you are doing.

To enable automatic authorization of every IP that hits your proxy, set AUTO_AUTH = True in auth/settings.py and run service netflix-proxy-admin restart. This setting will effectively authorize any IP hitting your proxy IP with a web browser for the first time, including bots, hackers, spammers, etc. Upon successful authorization, the browser will be redirected to Google⁠.

The DNS service is configured with recursion turned on by default⁠, so after a successful authorization, anyone can use your VPS in DNS amplification attacks, which will probably put you in breach of contract with the VPS provider. You have been WARNED.

⁠Security

The build script automatically configures the system with DNS recursion turned on. This has security implications, since it potentially opens your DNS server to a DNS amplification attack, a kind of a DDoS attack⁠. This should not be a concern however, as long as the iptables firewall rules configured automatically by the build script for you remain in place. However if you ever decide to turn the firewall off, please be aware of this.

If you want to turn DNS recursion off, please be aware that you will need a mechanism to selectively send DNS requests for domains your DNS server knows about (i.e. netflix.com) to your VPS and send all of the other DNS traffic to your local ISP's DNS server. Something like Dnsmasq⁠ can be used for this and some Internet routers even have it built in. In order to switch DNS recursion off, you will need to build your system using the following command:

git clone https://github.com/ab77/netflix-proxy /opt/netflix-proxy && cd /opt/netflix-proxy && ./build.sh -r 0 -b 1
⁠Command Line Options

The following command line options can be optionaly passed to build.sh for additional control:

Usage: ./build.sh [-r 0|1] [-b 0|1] [-c <ip>] [-i 0|1] [-d 0|1] [-t 0|1] [-z 0|1] [-u <username>] [-p <password>] [-n <1..N>] [-s <subnet>]
        -r      enable (1) or disable (0) DNS recursion (default: 1)
        -b      grab docker images from repository (0) or build locally (1) (default: 0)
        -c      specify client-ip instead of being taken from ssh_connection
        -i      skip iptables steps
        -d      skip Docker steps
        -t      skip testing steps
        -s      specify IPv6 subnet for Docker (e.g. 2001:470:abcd:123::/64)
        -z      enable caching resolver (default: 0)
        -u      HE tunnel broker username
        -p      HE tunnel broker password
        -n      HE tunnel index (default: 1)

⁠Other Cloud Providers

⁠Locale Issues

Some pre-requisites require the locale to be set correctly and some provider OS images need extra help. If you get locale issues reported by Python and/or pip durin the build, try running the following first:

export LANGUAGE=en_US.UTF-8 && \
  export LANG=en_US.UTF-8 && \
  export LC_ALL=en_US.UTF-8 && \
  locale-gen en_US.UTF-8 && \
  sudo dpkg-reconfigure locales

The following is based on a Debian image provided by Vultr, but should in theory work on any Debian distribution. Do not enable native IPv6 on the host.

  1. Head over to Vultr⁠ to create an account.
  2. Create a compute instance in a location closest to you using Debian 8 x64 (jessie) image.
  3. Create a free tunnel broker⁠ account.
  4. Create a regular tunnel⁠.
  5. Set the IPv4 Endpoint to the IP address of your Vultr instance, pick a tunnel server closest to you and click Create Tunnel.
  6. SSH to your server and run ping6 netflix.com; if you get Network is unreachable proceed to the next step, otherwise remove native IPv6 first.
  7. Run: apt-get update && apt-get -y install vim dnsutils curl sudo git && curl -sSL https://get.docker.com/ | sh && git clone https://github.com/ab77/netflix-proxy /opt/netflix-proxy && cd /opt/netflix-proxy && ./build.sh -u <tunnelbroker-username> -p <tunnelbroker-password>, making sure to specify your HE tunnel username and password correctly.
  8. Make sure to record the credentials for the netflix-proxy admin site.
  9. Set your DNS server to the IP given at the end of the script, then go to this⁠ site to make sure the same IP is displayed.
  10. Finally, enjoy Netflix and others out of region.
  11. Enjoy or raise a new issue⁠ if something doesn't work quite right (also #netflix-proxy on freenode⁠).

The following is based on a Debian or Ubuntu OS images provided by RamNode. Do not enable native IPv6 on the host.

  1. Head over to RamNode⁠ to create an account and buy a KVM VPS in a location closest to you (OpenVZ won't work).
  2. Log into the VPS Control Panel and (re)install the OS using Ubuntu 14.04 x86_64 Server Minimal or Debian 8.0 x86_64 Minimal image.
  3. Create a free tunnel broker⁠ account.
  4. Create a regular tunnel⁠.
  5. Set the IPv4 Endpoint to the IP address of your RamNode VPS, pick a tunnel server closest to you and click Create Tunnel.
  6. SSH to your server and run ping6 netflix.com; if you get Network is unreachable proceed to the next step, otherwise remove native IPv6 first.
  7. Run: apt-get update && apt-get -y install vim dnsutils curl sudo git && curl -sSL https://get.docker.com/ | sh && git clone https://github.com/ab77/netflix-proxy /opt/netflix-proxy && cd /opt/netflix-proxy && ./build.sh -u <tunnelbroker-username> -p <tunnelbroker-password>, making sure to specify your HE tunnel username and password correctly.
  8. Make sure to record the credentials for the netflix-proxy admin site.
  9. Set your DNS server to the IP given at the end of the script, then go to this⁠ site to make sure the same IP is displayed.
  10. Finally, enjoy Netflix and others out of region.
  11. Enjoy or raise a new issue⁠ if something doesn't work quite right (also #netflix-proxy on freenode⁠).

(untested) The following is based on a standard Ubuntu image provided by Linode, but should work on any Linux distribution without Docker installed. Do not enable native IPv6 on the host or disable it post-build and before moving onto step 7.

  1. Head over to Linode⁠ and sign-up for an account.
  2. Create a new Linode in a location closest to you and deploy an Ubuntu 14-04 LTS image into it.
  3. Create a free tunnel broker⁠ account.
  4. Create a regular tunnel⁠.
  5. Set the IPv4 Endpoint to the IP address of your Linode, pick a tunnel server closest to you and click Create Tunnel.
  6. SSH to your server and run ping6 netflix.com; if you get Network is unreachable proceed to the next step, otherwise remove native IPv6 first.
  7. Run: curl -sSL https://get.docker.com/ | sh && git clone https://github.com/ab77/netflix-proxy /opt/netflix-proxy && cd /opt/netflix-proxy && ./build.sh -u <tunnelbroker-username> -p <tunnelbroker-password>, making sure to specify your HE tunnel username and password correctly.
  8. Make sure to record the credentials for the netflix-proxy admin site.
  9. Set your DNS server to the IP given at the end of the script, then go to this⁠ site to make sure the same IP is displayed.
  10. Finally, enjoy Netflix and others out of region.
  11. Enjoy or raise a new issue⁠ if something doesn't work quite right (also #netflix-proxy on freenode⁠).

(untested) The following is based on a standard Ubuntu image provided by DreamHost, but should work on any Linux distribution without Docker installed and running under non-root user (e.g. Amazon Web Services). Do not enable native IPv6 on the host.

  1. Head over to DreamHost⁠ and sign-up for an account.
  2. Find the DreamCompute or Public Cloud Computing section and launch an Ubuntu 14-04-Trusty instance in a location closest to you.
  3. Make sure to add an additional firewall rule to allow DNS: Ingress IPv4 UDP 53 0.0.0.0/0 (CIDR)
  4. Also add a Floating IP to your instance.
  5. Create a free tunnel broker⁠ account.
  6. Create a regular tunnel⁠.
  7. Set the IPv4 Endpoint to the IP address of your instance, pick a tunnel server closest to you and click Create Tunnel.
  8. SSH to your server and run ping6 netflix.com; if you get Network is unreachable proceed to the next step, otherwise remove native IPv6 first.
  9. Run: curl -sSL https://get.docker.com/ | sh && sudo usermod -aG docker $(whoami | awk '{print $1}') && sudo git clone https://github.com/ab77/netflix-proxy /opt/netflix-proxy && cd /opt/netflix-proxy && ./build.sh -u <tunnelbroker-username> -p <tunnelbroker-password>, making sure to specify your HE tunnel username and password correctly.
  10. Make sure to record the credentials for the netflix-proxy admin site.
  11. Set your DNS server to the IP given at the end of the script, then go to this⁠ site to make sure the same IP is displayed.
  12. Finally, enjoy Netflix and others out of region.
  13. Enjoy or raise a new issue⁠ if something doesn't work quite right (also #netflix-proxy on freenode⁠).

The following is based on (slightly broken) Ubuntu image provided by Gandi using root login with SSH key only (no password). For default non-root admin login, adjust step 8 to use sudo where nesessary. Disable native IPv6 on the host as Gandi enable it by default.

  1. Head over to Gandi⁠ to create a virtual server.
  2. Create a free tunnel broker⁠ account.
  3. Create a regular tunnel⁠.
  4. Set the IPv4 Endpoint to the IP address of your server, pick a tunnel server in the US and click Create Tunnel.
  5. SSH to your server and run ping6 netflix.com; if you get Network is unreachable proceed to the next step, otherwise remove native IPv6 first.
  6. Run: apt-get -y update && apt-get -y install vim dnsutils curl sudo git && export LANGUAGE=en_US.UTF-8 && export LANG=en_US.UTF-8 && export LC_ALL=en_US.UTF-8 && locale-gen en_US.UTF-8 && sudo apt-get -y install language-pack-id && sudo dpkg-reconfigure locales && curl -sSL https://get.docker.com/ | sh && git clone https://github.com/ab77/netflix-proxy /opt/netflix-proxy && cd /opt/netflix-proxy && ./build.sh -u <tunnelbroker-username> -p <tunnelbroker-password>, making sure to specify your HE tunnel username and password correctly.
  7. Make sure to record the credentials for the netflix-proxy admin site.
  8. Set your DNS server to the IP given at the end of the script, then go to this⁠ site to make sure the same IP is displayed.
  9. Finally, enjoy Netflix and others out of region.
  10. Enjoy or raise a new issue⁠ if something doesn't work quite right (also #netflix-proxy on freenode⁠).
⁠Microsoft Azure (advanced)

The following has not been tested and is based on a standard Ubuntu image provided by Microsoft Azure using cloud-harness automation tool I wrote a while back and assumes an empty Microsoft Azure subscription.

  1. Head over to Microsoft Azure⁠ and sign-up for an account.
  2. Get Python⁠.
  3. On your workstation, run git clone https://github.com/ab77/cloud-harness.git /opt/cloud-harness.
  4. Follow cloud-harness Installation and Configuration⁠ section to set it up.
  5. Create⁠ a storage account.
  6. Create⁠ a new hosted service.
  7. Add⁠ a hosted service certificate for SSH public key authentication
  8. Create⁠ a reserved ip address.
  9. Create⁠ a virtual network.
  10. Create⁠ a Ubuntu 14.04 LTS virtual machine as follows:
    ./cloud-harness.py azure --action create_virtual_machine_deployment \
    --service <your hosted service name> \
    --deployment <your hosted service name> \
    --name <your virtual machine name> \
    --label 'Netflix proxy' \
    --account <your storage account name> \
    --blob b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04-LTS-amd64-server-20140414-en-us-30GB \
    --os Linux \
    --network VNet1 \
    --subnet Subnet-1 \
    --ipaddr <your reserved ipaddr name> \
    --size Medium \
    --ssh_auth \
    --disable_pwd_auth \
    --verbose
  1. Use the Azure Management Portal⁠ to add DNS (UDP), HTTP (TCP) and HTTPS (TCP) endpoints and secure them to your home/work/whatever IPs using the Azure ACL feature.
  2. SSH to your VM as azureuser using custom public TCP port (not 22) and use any non-root user Ubuntu instructions to build/install netflix-proxy.
⁠Automated Tests

I've linked this project with Travis CI to automatically test the build. The helper Python script __testbuild.py now runs automatically after every commit. This script deploys a test Droplet and then runs a serious of tests to verify (a) that both Docker containers start; and (b) the built.sh script outputs the correct message at the end. The test Droplet is destroyed and the end of the run.

The __testbuild.py script can also be used to programatically deploy Droplets from the command line as follows:

python ./__testbuild.py digitalocean --api_token abcdef0123456789... --fingerprint 'aa:bb:cc:dd:...' --region 'abc1'
  • --api_token abcdef0123456789... is your DigitalOCean API v2 token, which you can generate here⁠.
  • --fingerprint aa:bb:cc:dd:... are your personal SSH key fingerprint(s) quoted and separated by spaces. You can manage your SSH keys here⁠. If you don't specify a fingerprint, it will default to my test one, which means you won't be able to SSH into your Droplet.
  • --region abc1 is the region where you want the Droplet deployed. The default is nyc3, but you can use --list_regions to see the available choices.
  • --help parameter will also list all of the available command line options to pass to the script.

Note, you will need a working Python 2.7 environment and the modules listed in requirements.txt (run pip install -r requirements.txt).

⁠IPv6 and Docker

This solution uses IPv6 downstream from the proxy to unblock IPv6 enabled providers, such as Netflix. No IPv6 support on the client is required for this to work, only the VPS must public IPv6 connectivity. You may also need to turn off IPv6 on your local network (and/or relevant devices).[n6] Having said that, the current iteration uses HE Eectric's free tunnel broker service to provide IPv6 connectivity, since HE Electric is geo-located in the US, Netflix geoblocking (or geo-bollocking, if you like), allows the traffic through.

+----------+                  +-----------+                 +-----------------+
|          |                  |           |                 |                 |
|  client  | +--------------> |   proxy   | +-------------> |  Netflix, etc.  |
|          |      (ipv4)      |           |      (ipv6)     |                 |
+----------+                  +-----------+                 +-----------------+

When IPv6 public address is present on the host, Docker is configured with public IPv6 support. This is done by assuming the smallest possible IPv6 allocation, dividing it further by two and assigning the second half to the Docker system. Network Discovery Protocol (NDP) proxying is required for this to work, since the second subnet can not be routed[n9]. Afterwards, Docker is running in dual-stack mode, with each container having a public IPv6 address. This approach seems to work in most cases where native IPv6 is used. If IPv6 is provided via a tunnel, Docker subnet can not be reliably calculated and must be specified using -s parameter to the build.sh script. If IPv6 is not enabled at all, the VPS is built with IPv4 support only.

⁠RamNode

RamNode (and any other provider which uses SolusVM as its VPS provisioning system[n10]) assign a /64 subnet to the VPS, but don't route it. Instead, individual addresses must be added in the portal if they are to be used on the host. After speaking with RamNode support, it appears this is a side-effect of MAC address filtering, which prevents IP address theft. This means that even though the subnet can be further divided on the host, only the main IPv6 address bound to eth0 is ever accessible from the outside and none of the IPv6 addresses on the bridges below can communicate over IPv6 to the outside.

To demonstrate this behavour, follow these steps:

IPV6_SUBNET=<al

Tag summary

Content type

Image

Digest

Size

196 MB

Last updated

about 9 years ago

docker pull intersoftlab/iptables-auth