Header
Home | Set as homepage | Add to favorites
  Search the Site     » Advanced Search
Sections
Syndication


Blogroll:

||||| ALL Cisco-Network ARTICLES |||||  
CCIE Journey,
The CCIE Journey,


Device Interfaces

Sep 09,2009 by alperen

image

Device Interfaces

A key concept in all NAT translations is identifying the internal (inside) interface(s) and the external (outside) interface(s). NAT needs to know which interfaces are connected to inside networks and which are connected to outside networks. Only packets moving between inside and outside interfaces can be translated. At least one inside interface and one outside interface for each border router must be defined. The following configuration additions would be typical for a perimeter router with a single serial connection to the Internet and a single LAN:

interface Serial0/0
 ip nat outside
!
interface FastEthernet0/0
 ip nat inside

Outside interfaces should never be included in internal route tables and must remain unknown to internal hosts. Similarly, internal addresses should never be advertised or shared with the outside world. The internal interface typically is either the default gateway for hosts that share that network or the next-hop address for default routes set on other internal routers.


134 times read

Related news

» Configuring Basic NAT Functionality
by admin posted on Jul 21,2008
» Inside Network 2
by alperen posted on Aug 28,2009
» Allocating External Addresses Statically
by admin posted on Jul 21,2008
» Configuring Static NAT
by alperen posted on Nov 27,2008
» Perimeter Router Networks
by alperen posted on Aug 28,2009
Did you enjoy this article?
(total 0 votes)

comment Comments (0 posted) 

More Top News
CCSP-Cisco Certified Security Professional
Most Popular
Most Commented
Featured Author