Showing posts with label routing. Show all posts
Showing posts with label routing. Show all posts

Thursday, 13 August 2015

Ubiquiti AirOS Hairpin NAT


When setting up a port forward (Destination NAT) on a Ubiquiti AirOs device, you will find that users inside your network will not be able to use the WAN IP to access the internal device. This is because you need to add what is known as a "Hairpin NAT". Read below for instructions on how to do that, and why it is necessary.

Wednesday, 21 January 2015

Mikrotik Netflix selective Routing

16:45 Posted by Jurgens Krause , , , 13 comments

If you live in a country without Netflix, you are forced to use a VPN to get Netflix access. Unfortunately there is no easy way to route Netflix traffic exclusively. The scripts below will help to build an address list of IP's to route through the tunnel. It should work with any VPN provider

Thursday, 26 June 2014

Static Netflix Routes

12:18 Posted by Jurgens Krause , , , 5 comments


A lot of people have multiple internet connections and use static routing to determine which connection a certain application uses. This is also true if you use a VPN connection to get access to services like Netflix/Hulu or other geo-locked services.

I have created this route list which works well with UnoTelly, but should work equally well for any other provider.

Tuesday, 17 December 2013

Routing Steam Traffic with Mikrotik

09:56 Posted by Jurgens Krause , , 2 comments
For people living in third world economies, where uncapped high speed broadband internet is only a myth, we are forced to come up with creative means of managing our bandwidth.

The scenario is this:
You have two internet connections, one, a high speed capped internet connection, the other a low speed uncapped option. You would want all game and Steam client traffic to run over the high speed connection, but all Steam downloads have to be routed through the slow uncapped connection. We assume that the default route is through the uncapped connection, and only specific traffic gets routed over the high speed link.

From the Steam website you can find the following port information:


Steam Client:
  • UDP 27000 to 27015 inclusive (Game client traffic)
  • UDP 27015 to 27030 inclusive (Typically Matchmaking and HLTV)
  • TCP 27014 to 27050 inclusive (Steam downloads)
  • UDP 4380

Dedicated or Listen Servers

  • TCP 27015 (SRCDS Rcon port)
Steamworks P2P Networking and Steam Voice Chat
  • UDP 3478 (Outbound)
  • UDP 4379 (Outbound)
  • UDP 4380 (Outbound)
Additional Ports for Call of Duty: Modern Warfare 2 Multiplayer
  • UDP 1500 (outbound)
  • UDP 3005 (outbound)
  • UDP 3101 (outbound)
  • UDP 28960
Now, based on this we want to route all steam traffic apart from Steam Downloads (TCP 27015-27050) via the high speed link, so we start by marking the packets that we want to route to our high speed link:

Having marked the packets appropriately, we want to tell the Mikrotik firewall to route it through a specific gateway:
That's it, you will now be able to use Steam voice chat and the Steam Client through your high speed link with downloads running over you uncapped connection.