Hot Downloads

Welcome, Guest
Username: Password: Remember me

TOPIC: Proxy vs NAT

Proxy vs NAT 11 years 3 days ago #10241

I was asked in class today as to why Proxy server is no more popular as compared to NAT? As I am new to this area I went in total blur. Any insight?
The administrator has disabled public write access.

Re: Proxy vs NAT 11 years 3 days ago #10247

  • DaLight
  • DaLight's Avatar
  • Offline
  • Honored Member
  • Posts: 1302
  • Karma: 1
Probably because proxy servers have traditionally masked the real address of the client machine, a function which NAT by definition performs. Of course the router public IP will still be visible.
The administrator has disabled public write access.

Re: Proxy vs NAT 11 years 3 days ago #10251

  • nske
  • nske's Avatar
  • Offline
  • Expert Member
  • Posts: 613
  • Karma: 0
hmm good question. Here are a couple of points I can think of.

- A proxy's functionality scope is much more limited and specific, NAT technology can be used more flexibly than simply for "allowing a host of some internal network to gain access to resources of some external network" (check the excellent texts about Network Address Translation on this site for more info).

- NAT works on a more basic level than typical proxy implementations and this results in better compatibility with network protocols of higher level.

- For the same reason, proxy server implementations tend to be protocol-specific, offering support for certain application layer protocols like HTTP and FTP.

- There are also proxy implementations like SOCKS, which can serve for most types of data, but even these require additional support (and configuration) from each application. NAT technology works transparently to the end user/application, it is easier to implement and requires no extra configuration to use.

- NAT because it works in a basic level, causes much less overhead than proxies. In a sense, most proxy implementations will "parse" fully through their engine any content you've requested, before they deliver it to you. This is much slower than simply changing a couple of header fields to individual packets passing through some interface -like NAT does.

On the other hand, proxies offer some other advantages like more powerfull control capabilities over the traffic (since it is processed at a higher level), and allow the possibility to cache data locally for the same reason.
The administrator has disabled public write access.

Proxies 11 years 2 days ago #10260

  • TheBishop
  • TheBishop's Avatar
  • Offline
  • Moderator
  • Posts: 1719
  • Thank you received: 8
  • Karma: 5
As nske wrote,
On the other hand, proxies offer some other advantages like more powerfull control capabilities over the traffic (since it is processed at a higher level)
. This also means that a well-written proxy can also serve as a security device - for example an HTTP proxy can examine the connection request coming in and refuse to pass it through to the web server if it looks dubious. The proxies in the Cyberguard firewall product do this, for example. In contrast, NAT is just a means of allowing the connection to be made by supporting the address translation/mapping
The administrator has disabled public write access.
Time to create page: 0.090 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup