cc/td/doc/product/software/ios121/121cgcr/dialns_c
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring Cisco Easy IP

Configuring Cisco Easy IP

This chapter describes how to configure the Cisco Easy IP feature. It includes the following main sections:

For a complete description of the Cisco Easy IP commands in this chapter, see the Cisco IOS Dial Services Command Reference publication. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.

Cisco Easy IP Overview

Cisco Easy IP enables transparent and dynamic IP address allocation for hosts in remote environments using the following functionality:

With the Cisco IOS Easy IP, a Cisco router automatically assigns local IP addresses to remote hosts (such as small office, home office or SOHO routers) using DHCP with the Cisco IOS DHCP server, automatically negotiates its own registered IP address from a central server via PPP/IPCP, and uses PAT functionality to enable all SOHO hosts to access the Internet using a single registered IP address. Because Cisco IOS Easy IP uses existing port-level multiplexed NAT functionality within Cisco IOS software, IP addresses on the remote LAN are invisible to the Internet, making the remote LAN more secure.

Cisco Easy IP provides the following benefits:

Figure 41 shows a typical scenario for using the Cisco Easy IP feature.


Figure 41: Telecommuter and Branch Office LANs Using Easy IP


Steps 1 through 4 show how Cisco Easy IP works:


Step 1 When a SOHO host generates "interesting" traffic (as defined by Access Control Lists) for dialup (first time only), the Easy IP router requests a single registered IP address from the access server at the central site via PPP/IPCP. Refer to
Figure 42.


Figure 42: Easy IP Router Requests a Dynamic Global IP Address


Step 2 The central site router replies with a dynamic global address from a local DHCP IP address pool. Refer to Figure 43.


Figure 43: Dynamic Global IP Address Delivered to the Easy IP Router


Step 3 The Cisco Easy IP router uses port-level NAT functionality to automatically create a translation that associates the registered IP address of the WAN interface with the private IP address of the client. Refer to Figure 44.


Figure 44: Port-Level NAT Functionality Used for IP Address Translation


Step 4 The remote hosts contain multiple static IP addresses while the Easy IP router obtains a single registered IP address using PPP/IPCP. The Easy IP router then creates port-level multiplexed NAT translations between these addresses so that each remote host address (inside private address) is translated to a single external address assigned to the Easy IP router. This many-to-one address translation is also called port-level multiplexing or PAT. Note that the NAT port-level multiplexing function can be used to conserve global addresses by allowing the remote routers to use one global address for many local addresses. Refer to Figure 45.



Figure 45: Multiple Private Internal IP Addresses Bound to a Single Global IP Address


Cisco Easy IP Configuration Task List

Complete the following tasks before using Cisco Easy IP:

For information about configuring ISDN switch types, see the chapter "Setting Up ISDN Basic Rate Service" in the Cisco IOS Dial Services Configuration Guide: Terminal Services publication. For information about configuring static routes, see the chapter "Configuring IP Services" in the
Cisco IOS IP and IP Routing Configuration Guide publication.

The Cisco IOS DHCP server supports both DHCP and BOOTP clients and supports finite and infinite address lease periods. DHCP address binding information is stored on a remote host via remote copy protocol (RCP), File Transfer Protocol (FTP), or Trivial File Transfer Protocol (TFTP). See the Cisco IOS IP and IP Routing Configuration Guide for DHCP configuration instructions.

In its most simple configuration, a Cisco Easy IP router or access server will have a single LAN interface and a single WAN interface. Based on this model, you must complete the following tasks in the following sections to use Cisco Easy IP:

For configuration examples, see the section "Cisco Easy IP Configuration Examples" at the end of this chapter.

Defining the NAT Pool

The first step in enabling Cisco Easy IP is to create a pool of internal IP addresses to be translated. To define the NAT pool, use the following commands in global configuration mode:

Command Purpose

Step 1

access-list access-list-number permit source 
[source-wildcard]

Defines a standard access list permitting those addresses that are to be translated.

Step2

ip nat inside source list access-list-number 
interface dialer-name overload

Establishes dynamic source translation, identifying the access list defined in the prior step.

For information about creating access lists, refer to the chapter "Configuring IP Services" in the CiscoIOS IP and IP Routing Configuration Guide.

Configuring the LAN Interface

To configure the LAN interface, use the following commands in interface configuration mode:

Command Purpose

Step1

interface type number

Selects a specific LAN interface.

Step2

ip address address mask

Defines the IP address and subnet mask for this interface.

For information about assigning IP addresses and subnet masks to network interfaces, refer to the chapter "Configuring IP Services" in the Cisco IOS IP and IP Routing Configuration Guide.

Defining NAT for the LAN Interface

To ensure that the LAN interface is connected to the inside network (and therefore subject to NAT), use the following command in interface configuration mode:

Command Purpose
ip nat inside

Defines the interface as internal for NAT.

Configuring the WAN Interface

To configure the WAN interface, use the following commands in interface configuration mode:

Command Purpose

Step1

interface type number

Selects the WAN interface.

Step2

no ip address

Removes any associated IP address from this interface.

Step3

encapsulation ppp

Selects PPP as the encapsulation method for this interface.

Step4

dialer pool-member 
number

Binds the WAN interface to the dialer interface.

Enabling PPP/IPCP Negotiation

To enable PPP/IPCP negotiation on the dialer interface, use the following commands in interface configuration mode:

Command Purpose

Step1

interface dialer-name

Selects the dialer interface.

Step2

ip address negotiated

Enables PPP/IPCP negotiation for this interface.

Defining NAT for the Dialer Interface

To define that the dialer interface is connected to the outside network, use the following commands in interface configuration mode:

Command Purpose

Step1

interface dialer-name

Selects the dialer interface.

Step2

ip nat outside

Defines the interface as external for network address translation.

Configuring the Dialer Interface

To configure the dialer interface information, use the following commands in interface configuration mode:

Command Purpose

Step1

interface dialer-name

Selects the dialer interface.

Step2

dialer 
wait-for-carrier-time seconds

Specifies for a dialer interface the length of time the interface waits for a carrier before timing out.

Step3

dialer hold-queue 
packets

Creates a dialer hold queue and specifies the number of packets to be held in it.

Step4

dialer remote-name 
username

Specifies the remote router Challenge Handshake Authentication Protocol (CHAP) authentication name.

Step5

dialer idle-timeout 
seconds

Specifies the amount of idle time that can pass before calls to the central access server are disconnected. See the next section "Timeout Considerations," for more details on this setting.

Step6

dialer string 
dialer-string

Specifies the telephone number required to reach the central access server.

Step7

dialer pool number

Specifies the dialing pool to use.

Step8

dialer-group 
group-number

Assigns the dialer interface to a dialer group.

Timeout Considerations

Dynamic NAT translations time out automatically after a predefined default period. Although configurable, with the port-level NAT functionality in Easy IP, Domain Name System (DNS) User Datagram Protocol (UDP) translations time out after 5 minutes, while DNS translations time out after 1 minute by default. TCP translations time out after 24 hours by default, unless a TCP Reset (RST) or TCP Finish (FIN) is seen in the TCP stream, in which case the translation times out after 1 minute.

If the Cisco IOS Easy IP router exceeds the dialer idle-timeout period, it is expected that all active TCP sessions were previously closed via an RST or FIN. NAT times out all TCP translations before the CiscoEasy IP router exceeds the dialer idle-timeout period. The router then renegotiates another registered IP address the next time the WAN link is brought up, thereby creating new dynamic NAT translations that bind the IP addresses of the LAN host to the newly negotiated IP address.

Cisco Easy IP Configuration Examples

The following example shows how to configure BRI interface 0 (shown as interface bri0) to obtain its IP address via PPP/IPCP address negotiation:

! The following command defines the NAT pool.
ip nat inside source list 101 interface dialer1 overload
!
! The following commands define the ISDN switch type.
isdn switch type vn3
isdn tei-negotiation first-call
!
!The following commands define the LAN address and subnet mask.
interface ethernet0
ip address 10.0.0.4 255.0.0.0
 
!The following command defines ethernet0 as internal for NAT.
ip nat inside
!
!The following commands binds the physical interface to the dialer1 interface.
interface bri0
no ip address
encapsulation ppp
dialer pool-member 1
!
interface dialer1
!
!The following command enables PPP/IPCP negotiation for this interface.
ip address negotiated
encapsulation ppp
!
!The following command defines dialer1 interface as external for NAT.
ip nat outside
dialer remote-name dallas
dialer idle-timeout 180
!
!The following command defines the dialer string for central access server.
dialer string 4159991234
dialer pool 1
dialer-group 1
!
!The following commands define the static route to the WAN interface.
ip route 0.0.0.0 0.0.0.0 dialer1
access-list 101 permit ip 10.0.0.0 0.255.255.255 any
dialer-list 1 protocol ip list 101
 

The following example shows how to configure an asynchronous interface (interface async1) to obtain its IP address via PPP/IPCP address negotiation:

! This command defines the NAT pool.
ip nat inside source list 101 interface dialer 1 overload
!
!The following commands define the LAN IP address and subnet mask.
interface ethernet0
ip address 10.0.0.4 255.0.0.0
!
!The following command defines ethernet0 as internal for NAT.
ip nat inside
!
!The following commands bind the physical dialer1 interface.
interface async1
no ip address
encapsulation ppp
async mode dedicated
dialer pool-member 1
!
interface dialer1
!
!The following command enables PPP/IPCP negotiation for this interface.
ip address negotiated
encapsulation ppp
!
!The following command defines dialer1 interface as external for NAT.
ip nat outside
dialer wait-for-carrier-time 30
dialer hold-queue 10
dialer remote-name dallas
dialer idle-timeout 180
!
!The following command defines the dialer string for central access server.
dialer string 4159991234
dialer pool 1
dialer-group 1
!
!The following commands define the static route to the WAN interface.
ip route 0.0.0.0 0.0.0.0 dialer1
access-list 101 permit ip 10.0.0.0 0.255.255.255 any
dialer-list 1 protocol ip list 101


hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Jul 18 15:01:32 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.