NAT

NAT (network address translation) - (see Wikipedia) is the process of re-writing the source and/or destination addresses of IP packets. Most systems using NAT do so in order to enable multiple hosts on a private network to access the Internet using a single public IP address.

What is a diffrence between NAT implementation in TMeter and third-party NAT implementations?

The integration of NAT and TMeter solves very important task - an accounting "clear" traffic of NAT router (without traffic of users on a private network). So, if you have a job place on a computer acting as the Internet gateway with running TMeter, you can count the traffic of the Internet gateway without the traffic of other uses from the private network.

TMeter NAT engine doesn't require specific IP addresses for the private network (in difference with "Internet Connection Sharing" service of Microsoft Windows 2000 Professional, Windows XP and Windows Vista which assign the IP address 192.168.0.1 to the private network interface).

 Note

• The current implementation of NAT supports only ICMP, TCP, UDP and GRE protocols.
• TCP/IP forwarding must be enabled on the computer running NAT (see details...)
• Packets are processed by NAT only on the public network interface.
• Traffic Shaper doesn't work for packets rewritten by NAT (consider using Traffic Shaper on a private network interface)
• Users behind NAT should use passive FTP mode for outgoing FTP connections.