DVR Security Systems Wholesale Quote  DVR CCTV, IP, Capture Cards with   POE Client Security Software by 128 80 64  32 16 8 4 channel real-time   HIKVision H.264  DSS, Kodicom, Aventura, DigiNet, NUUO, Avermedia, DVW, Hybrid, XOS, Linux,  GeoVision, Digital Video Witness, KCard, DF, HD, and ViewMax.  Cameras by Sony, Sharp, GE, Cop, Bosch, Vitek, KT & C, FLIR, GEN IV,  Honeywell, Thermal Image Cameras, Video Analytics,  Everfocus, Pelco, PTZ's, Wireless Cameras,  Spy Cameras, Dedicated Micros, Panasonic, Titan, samsung, Wide Dynamic Range, HD, Police Extreme, SAY much more.       

Remote Viewing A DVR from Behind a NAT Router or How Network Address Translation Works

The DV Series DVR has several advanced features that allow it to support remote access to live & stored video images from remote sites via the Internet.  The DV Series DVR supports dynamic IP addressing and Network Address Translation (NAT) routers. This application note will explain how to configure a DV Series DVR to work with consumer and commercial NAT routers, which in turn allows the user to access a DV Series DVR through a cable modem or DSL line. This application note assumes that you have a basic working knowledge of Internet networking. Advanced knowledge of Internet issues is not required.

Background Information

If you are reading this article, you are most likely connected to the Internet and viewing it at the DVSS Web site. There's a very good chance that you are using Network Address Translation (NAT) right now.

The Internet has grown larger than anyone ever imagined it could be. Although the exact size is unknown, the current estimate is that there are about 100 million hosts and more than 350 million users actively on the Internet. That is more than the entire population of the United States! In fact, the rate of growth has been such that the Internet is effectively doubling in size each year.  So what does the size of the Internet have to do with NAT? Everything! For a computer to communicate with other computers and Web servers on the Internet, it must have an IP address. An IP address (IP stands for Internet Protocol) is a unique 32-bit number that identifies the location of your computer on a network. Basically, it works like your street address -- as a way to find out exactly where you are and deliver information to you.

When IP addressing first came out, everyone thought that there were plenty of addresses to cover any need. Theoretically, you could have 4,294,967,296 unique addresses (2³²). The actual number of available addresses is smaller (somewhere between 3.2 and 3.3 billion) because of the way that the addresses are separated into classes, and because some addresses are set aside for multicasting, testing or other special uses.

With the explosion of the Internet and the increase in home networks and business networks, the number of available IP addresses is simply not enough. The obvious solution is to redesign the address format to allow for more possible addresses. This is being developed (called IPv6), but will take several years to implement because it requires modification of the entire infrastructure of the Internet.   

This is where NAT (RFC 1631) comes to the rescue. Network Address Translation allows a single device, such as a router, to act as an agent between the Internet (or "public network") and a local (or "private") network. This means that only a single, unique IP address is required to represent an entire group of computers.  But the shortage of IP addresses is only one reason to use NAT. Let's take a closer look at NAT and exactly what it can do...  

What Does NAT Do?
NAT is like the receptionist in a large office. Let's say you have left instructions with the receptionist not to forward any calls to you unless you request it. Later on, you call a potential client and leave a message for that client to call you back. You tell the receptionist that you are expecting a call from this client and to put her through.

The client calls the main number to your office, which is the only number the client knows. When the client tells the receptionist that she is looking for you, the receptionist checks a lookup table that matches your name with your extension. The receptionist knows that you requested this call, and therefore forwards the caller to your extension.

Developed by Cisco, Network Address Translation is used by a device (firewall, router or computer) that sits between an internal network and the rest of the world. NAT has many forms and can work in several ways:

• Static NAT - Mapping an unregistered IP address to a registered IP address on a one-to-one basis. Particularly useful when a device needs to be accessible from outside the network.

• Dynamic NAT - Maps an unregistered IP address to a registered IP address from a group of registered IP addresses.

• Overloading - A form of dynamic NAT that maps multiple unregistered IP addresses to a single registered IP address by using different ports. This is known also as PAT (Port Address Translation), single address NAT or port-level multiplexed NAT.

• Overlapping - When the IP addresses used on your internal network are registered IP addresses in use on another network, the router must maintain a lookup table of these addresses so that it can intercept them and replace them with registered unique IP addresses. It is important to note that the NAT router must translate the "internal" addresses to registered unique addresses as well as translate the "external" registered addresses to addresses that are unique to the private network. This can be done either through static NAT or by using DNS and implementing dynamic NAT.

The internal network is usually a LAN (Local Area Network), commonly referred to as the stub domain. A stub domain is a LAN that uses IP addresses internally. Most of the network traffic in a stub domain is local, so it doesn't travel outside the internal network. A stub domain can include both registered and unregistered IP addresses. Of course, any computers that use unregistered IP addresses must use Network Address Translation to communicate with the rest of the world.

NAT can be configured in various ways. In the example below, the NAT router is configured to translate unregistered (inside, local) IP addresses that reside on the private (inside) network, to registered IP addresses. This happens whenever a device on the inside with an unregistered address needs to communicate with the public (outside) network.

• An ISP assigns a range of IP addresses to your company. The assigned block of addresses are registered, unique IP addresses and are called inside global addresses. Unregistered, private IP addresses are split into two groups. One is a small group (outside local addresses) that will be used by the NAT routers. The other, much larger group, known as inside local addresses, will be used on the stub domain. The outside local addresses are used to translate the unique IP addresses, known as outside global addresses, of devices on the public network.

• Most computers on the stub domain communicate with each other using the inside local addresses.
• Some computers on the stub domain communicate a lot outside the network. These computers have inside global addresses, which mean that they do not require translation.
• When a computer on the stub domain that has an inside local address wants to communicate outside the network, the packet goes to one of the NAT routers.
• The NAT router checks the routing table to see if it has an entry for the destination address. If it does, the NAT router then translates the packet and creates an entry for it in the address translation table. If the destination address is not in the routing table, the packet is dropped.
• Using an inside global address, the router sends the packet on to it's destination.
• A computer on the public network sends a packet to the private network. The source address on the packet is an outside global address. The destination address is an inside global address.
• The NAT router looks at the address translation table and determines that the destination address is in there, mapped to a computer on the stub domain.
• The NAT router translates the inside global address of the packet to the inside local address, and sends it to the destination computer.

NAT overloading utilizes a feature of the TCP/IP protocol stack, multiplexing, that allows a computer to maintain several concurrent connections with a remote computer (or computers) using different TCP or UDP ports. An IP packet has a header that contains the following information:

• Source Address - The IP address of the originating computer, such as 201.3.83.132
• Source Port - The TCP or UDP port number assigned by the originating computer for this packet, such as Port 1080
• Destination Address - The IP address of the receiving computer, such as 145.51.18.223
• Destination Port - The TCP or UDP port number that the originating computer is asking the receiving computer to open, such as Port 3021

The addresses specify the two machines at each end, while the port numbers ensure that the connection between the two computers has a unique identifier. The combination of these four numbers defines a single TCP/IP connection. Each port number uses 16 bits, which means that there are a possible 65,536 (2¹⁶) values. Realistically, since different manufacturers map the ports in slightly different ways, you can expect to have about 4,000 ports available.

Dynamic NAT and Overloading
Here is how dynamic NAT works:

• An internal network (stub domain) has been set up with IP addresses that were not specifically allocated to that company by IANA (Internet Assigned Numbers Authority), the global authority that hands out IP addresses. These addresses should be considered non-routable since they are not unique.
• The company sets up a NAT-enabled router. The router has a range of unique IP addresses given to the company by IANA.
• A computer on the stub domain attempts to connect to a computer outside the network, such as a Web server.
• The router receives the packet from the computer on the stub domain.
• The router saves the computer's non-routable IP address to an address translation table. The router replaces the sending computer's non-routable IP address with the first available IP address out of the range of unique IP addresses. The translation table now has a mapping of the computer's non-routable IP address matched with the one of the unique IP addresses.
• When a packet comes back from the destination computer, the router checks the destination address on the packet. It then looks in the address translation table to see which computer on the stub domain the packet belongs to. It changes the destination address to the one saved in the address translation table and sends it to that computer. If it doesn't find a match in the table, it drops the packet.
• The computer receives the packet from the router. The process repeats as long as the computer is communicating with the external system.

Here is how overloading works:

• An internal network (stub domain) has been set up with non-routable IP addresses that were not specifically allocated to that company by IANA.
• The company sets up a NAT-enabled router. The router has a unique IP address given to the company by IANA.
• A computer on the stub domain attempts to connect to a computer outside the network, such as a Web server.
• The router receives the packet from the computer on the stub domain.
• The router saves the computer's non-routable IP address and port number to an address translation table. The router replaces the sending computer's non-routable IP address with the router's IP address. The router replaces the sending computer's source port with the port number that matches where the router saved the sending computer's address information in the address translation table. The translation table now has a mapping of the computer's non-routable IP address and port number along with the router's IP address.
• When a packet comes back from the destination computer, the router checks the destination port on the packet. It then looks in the address translation table to see which computer on the stub domain the packet belongs to. It changes the destination address and destination port to the ones saved in the address translation table and sends it to that computer.
• The computer receives the packet from the router. The process repeats as long as the computer is communicating with the external system.
• Since the NAT router now has the computer's source address and source port saved to the address translation table, it will continue to use that same port number for the duration of the connection. A timer is reset each time the router accesses an entry in the table. If the entry is not accessed again before the timer expires, the entry is removed from the table.

Look at this table to see how the computers on a stub domain might appear to external networks.

As you can see, the NAT router stores the IP address and port number of each computer in the address translation table. It then replaces the IP address with its own registered IP address and the port number corresponding to the location, in the table, of the entry for that packet's source computer. So any external network sees the NAT router's IP address and the port number assigned by the router as the source-computer information on each packet.

You can still have some computers on the stub domain that use dedicated IP addresses. You can create an access list of IP addresses that tells the router which computers on the network require NAT. All other IP addresses will pass through untranslated.

The number of simultaneous translations that a router will support is determined mainly by the amount of DRAM (Dynamic Random Access Memory) it has. But since a typical entry in the address-translation table only takes about 160 bytes, a router with 4 MB of DRAM could theoretically process 26,214 simultaneous translations, which is more than enough for most applications.

IANA has set aside specific ranges of IP addresses for use as non-routable, internal network addresses. These addresses are considered unregistered (for more information check out RFC 1918: Address Allocation for Private Internets, which defines these address ranges). No company or agency can claim ownership of unregistered addresses or use them on public computers. Routers are designed to discard (instead of forward) unregistered addresses. What this means is that a packet from a computer with an unregistered address could reach a registered destination computer, but the reply would be discarded by the first router it came to.

There is a range for each of the three classes of IP addresses used for networking:

• Range 1: Class A - 10.0.0.0 through 10.255.255.255
• Range 2: Class B - 172.16.0.0 through 172.31.255.255
• Range 3: Class C - 192.168.0.0 through 192.168.255.255

Although each range is in a different class, you are not required to use any particular range for your internal network. It is a good practice, though, because it greatly diminishes the chance of an IP address conflict. 

Security and Administration
Implementing dynamic NAT automatically creates a firewall between your internal network and outside networks, or between your internal network and the Internet. NAT only allows connections that originate inside the stub domain. Essentially, this means that a computer on an external network cannot connect to your computer unless your computer has initiated the contact. You can browse the Internet and connect to a site, and even download a file; but somebody else cannot latch onto your IP address and use it to connect to a port on your computer.

In specific circumstances, Static NAT, also called inbound mapping, allows external devices to initiate connections to computers on the stub domain. For instance, if you wish to go from an inside global address to a specific inside local address that is assigned to your Web server, Static NAT would enable the connection.

Some NAT routers provide for extensive filtering and traffic logging. Filtering allows your company to control what type of sites employees visit on the Web, preventing them from viewing questionable material. You can use traffic logging to create a log file of what sites are visited and generate various reports from it.

NAT is sometimes confused with proxy servers, but there are definite differences between them. NAT is transparent to the source and to destination computers. Neither one realizes that it is dealing with a third device. But a proxy server is not transparent. The source computer knows that it is making a request to the proxy server and must be configured to do so. The destination computer thinks that the proxy server IS the source computer, and deals with it directly. Also, proxy servers usually work at layer 4 (transport) of the OSI Reference Model or higher, while NAT is a layer 3 (network) protocol. Working at a higher layer makes proxy servers slower than NAT devices in most cases.

A real benefit of NAT is apparent in network administration. For example, you can move your Web server or FTP server to another host computer without having to worry about broken links. Simply change the inbound mapping at the router to reflect the new host. You can also make changes to your internal network easily, because the only external IP address either belongs to the router or comes from a pool of global addresses.

NAT and DHCP (dynamic host configuration protocol ) are a natural fit. You can choose a range of unregistered IP addresses for your stub domain and have the DHCP server dole them out as necessary. It also makes it much easier to scale up your network as your needs grow. You don't have to request more IP addresses from IANA. Instead, you can just increase the range of available IP addresses configured in DHCP to immediately have room for additional computers on your network.

Multi-Homing
As businesses rely more and more on the Internet, having multiple points of connection to the Internet is fast becoming an integral part of their network strategy. Multiple connections, known as multi-homing, reduces the chance of a potentially catastrophic shutdown if one of the connections should fail.

In addition to maintaining a reliable connection, multi-homing allows a company to perform load-balancing by lowering the number of computers connecting to the Internet through any single connection. Distributing the load through multiple connections optimizes the performance and can significantly decrease wait times.

Multi-homed networks are often connected to several different ISPs (Internet Service Providers). Each ISP assigns an IP address (or range of IP addresses) to the company. Routers use BGP (Border Gateway Protocol), a part of the TCP/IP protocol suite, to route between networks using different protocols. In a multi-homed network, the router utilizes IBGP (Internal Border Gateway Protocol) on the stub domain side, and EBGP (External Border Gateway Protocol) to communicate with other routers.

Multi-homing really makes a difference if one of the connections to an ISP fails. As soon as the router assigned to connect to that ISP determines that the connection is down, it will reroute all data through one of the other routers.

NAT can be used to facilitate scalable routing for multi-homed, multi-provider connectivity. For more on multi-homing, see Cisco: Enabling Enterprise Multihoming.

For lots more information on NAT and related topics, check out the links on the next page.

Lots More Information!

Related Articles

• How Web Servers Work
• How LAN Switches Work
• How Routers Work
• How Ethernet Works
• How Home Networking Works
• How OSI Works

Example Using DV Series DVRs

The above illustration shows an alternative networking setup. In this setup, only the router has an IP address assigned by the ISP. The computers attached to the LAN have IP addresses assigned to them by the router. In addition, these IP addresses are "private" IP addresses that are not valid addresses on the open Internet. The router must be a special kind of router, called a "network address translation" (NAT) router. This type of router converts the IP address shown to the world on outbound connections from a private IP address to the IP address assigned to the router. It also maintains information that allows it to return requested data from the Internet to the machine that requested it.

 This illustration shows a diagram of how the private IP addresses of computers behind the router get converted to a valid address for communication over the Internet. You can think of an Internet communication as a person-to-person telephone call. The IP address is similar to a telephone number; it connects you with a destination but doesn't specify who you want to communicate with at that address. When you want to talk to a specific person on the remote side, you tell whoever answers the telephone that you want a particular person, and then you get to talk to that person. Similarly, when an Internet connection is made, you must specify an IP address and a port number. The port number is similar to saying you want to talk to a particular person. In this case, though, the port number is how you identify which "service" you want on the remote machine. The computer on the LAN is requesting a connection with port 80, which is a port reserved for Web servers. A computer on the LAN sends a packet out to the Internet through the NAT router. The computer uses its own IP address as the "from" address, but this address is invalid on the open Internet because it is a private IP address. The NAT router sees the private IP address and rewrites the "from" address on the packet with its own address, which is a valid address assigned by an ISP. The rewritten packet is then forwarded to the Internet. Port numbers play an important part in the translation. In figure 3, the LAN computer has sent a packet from port 20167 (this number is not important, but merely serves as a number we can refer to as we go). The router can either send this packet from its own port 20167, or it can send it from another port if port 20167 on the router is already in use. The router has sent the packet from port 31284. No matter what the router decides about which port to use, it remembers which port it used to send the packet

(31284 in this example), so any data packets sent in response to this packet get routed back to the computer that requested them. It can do this because the return packets will be sent to port 31284, which the router remembers was associated with port 20167.

The above illustration shows how Network Address Translation works for return packets. Note that the NAT router rewrites the packet "to" address information on return packets, because the remote side sent the packets to the router, not the computer on the LAN. Figure 4: NAT translation on return data packets outbound connections (where the computers behind the NAT router initiate the connection) are easy, because the router knows where the connection came from and where it is going. But what about inbound connections, where someone from the Internet wants to establish a connection with a computer behind the NAT router? This is a situation that is impossible to resolve, because the person from the Internet only knows router's IP address, not the IP address of any of the machines behind the router. Even if the person knew the actual IP address assigned to a particular computer behind the router, that information would be useless because all of those addresses are private addresses. No router between that person and the NAT router will pass along a request to or from any IP address in the private range. So how can we allow access to computers on the LAN through the NAT router? The answer is by using a technique called "port mapping" or sometimes "port forwarding." With this technique, you can tell the NAT router to send all requests for connections to a particular port to the same port on a particular IP address behind the router. For instance, you can configure the router to send all requests for a connection to port 2345 on the router's IP address to port 2345 on IP address 192.168.1.32. This ability allows us to expose a DV Series DVRs remote access features by setting up a port forwarding entry to forward connections to any given port to the appropriate DV Series DVR. Since the DV Series DVR software allows the user to specify which port is to be used for remote access, each DV Series DVR can listen on its own port, and the NAT router can be configured to connect remote users to the proper DV Series DVR.

Setting up a NAT network of DV Series DVRs

This section will explain how to set up a network of DV Series DVRs behind a NAT router and a cable modem. The first thing to do is connect the NAT router (such as a Linksys BEFSR41) to the cable modem and verify the basic operation of the router and the cable modem. Consult the router and cable modem documentation for instructions on how to do this. Once the router and cable mode are working properly, connect the DV Series DVRs to the router. The most common situation will be to configure the router to act as a DHCP (Dynamic Host Configuration Protocol) server, and to configure the DV Series DVRs to obtain their IP addresses automatically. The only problem with this setup, as you will see later, is that in order to configure the router to allow external access to the DV Series DVRs, the router must know the IP address of each DV Series DVR on the network. So the best thing to do is to assign an IP address to each DV Series DVR by hand. Choose an IP address in the same private IP address range as the router (usually 192.168.1.x or 192.168.0.x) but outside the range of IP addresses that the router will use for DHCP requests. For example, if you have configured the router to assign IP addresses in the range between 192.168.1.32 and 192.168.1.64, start assigning IP addresses to your DV Series DVRs at 192.168.1.65 or above.

The next step is to configure each DV Series DVR behind the NAT router to use a unique port number for remote access. For instance, you might set up DV Series DVR #1 to use port 9999 for remote access, DV Series DVR #2 to use port 9998, DV Series DVR #3 to use port 9997, etc. The actual numbers chosen are not important, but each DV Series DVR must have its own port to use for remote connections. You can configure the port setting on an DV Series DVR by clicking on the "telephone" icon on the tool bar or by selecting "Configure | Remote Access" from the menu bar. If you change the port number, you will have to restart that DV Series DVR before the change takes effect. The final step is to configure the NAT router to route incoming connections to the proper machine. Consult the documentation for your router, but most routers have a web-based configuration interface. Look for a tab that is labeled "port forwarding" or perhaps "external routing." Again, consult your router's documentation for full instructions. When you configure the router's port forwarding setup, you will need a list of all the DV Series DVRs connected to the router, along with the IP address and port number used for each DV Series DVR. Generally you will see a screen similar to the one in figure 5 below (this is a screenshot from a Linksys BEFSR11)

 These are screenshots from a Linksys Router’s configuration page. As an example, let's say you had three DV Series DVRs behind the router, configured as shown below.

Station IP Address Port Number

1.      192.168.1.128             9028

2.      192.168.1.129             9029

3.      192.168.1.130             9030

With this setup, you would enter information into the router's configuration screen so it looked like the one in illustration on the right. The important parts of the configuration are the port ranges, the protocol (TCP) and the IP Address. Remember to check the "enabled" box if your router has one. Some routers will have you specify a single port, while others will use a range of port numbers. For routers that use a single port, enter in the port you set for that DV Series DVR. For routers that use a range, enter the same port number for both the "high" and "low" values. The DV Series DVR uses the UDP protocol. You will have to set up the router for UDP. Once you have entered all the relevant information, click "Apply" or "submit" or "save" or whatever button is required to save your configuration. When the router returns to the configuration page, confirm that everything you have entered is correct, and proceed to testing.

Testing

In order to test the setup, you will need to attempt remote access from outside the router. The easiest way to do this is to have another person attempt the connection for you. Uses the Client Software provided and remotely connect to the router's IP address, not the private IP addresses you assigned to the DV Series DVRs. For example, if the router had been assigned IP address 64.34.27.23 and you wanted to connect to DV Series DVR #1 from the setup above, you would use the NetDVR to connect to 64.34.27.23, port 9028. The router would then pass this connection through to 92.168.1.128, port 9028, which would connect you to DV Series DVR #1.