Table Of Contents
Feature-by-Feature Router Configurations
Before You Configure Your Network
Configuring Basic Parameters
Configuring Global Parameters
Configuring the Ethernet Interfaces
Configuration Example
Verifying Your Configuration
Configuring a Console Line for the Router
Configuration Example
Verifying Your Configuration
Configuring Bridging
Configuration Example
Verifying Your Configuration
Configuring Routing
Configuring Static Routing
Configuration Example
Verifying Your Configuration
Configuring Dynamic Routing
Configuring RIP
Configuring IP Enhanced IGRP
Configuring PBR
Configuring PPPoE Support
Configuring PAP Authentication
Configuration Examples
Verifying Your Configuration
Configuring Network Address Translation
Configuring NAT
Configuration Example
Verifying Your Configuration
Configuring NAT with IPCP
Configuration Example
Verifying Your Configuration
Configuring Dynamic Host Configuration Protocol
Configuring the DHCP Server and Relay
Configuring the DHCP Server
Configuring the DHCP Relay
Configuring a DHCP Client
Configuration Example
Verifying Your Configuration
Configuring IP Multicasting
Configuration Example
Verifying Your Configuration
Configuring an Extended Access List
Configuration Example
Verifying Your Configuration
Configuring Network Time Protocol Support
Configuring IP Security and Generic Routing Encapsulation Tunneling
Configuration Example
Configuring Other Security Features
Configuring a RADIUS Client
Configuring TACACS+
Configuring Service Assurance Agent Support
Feature-by-Feature Router Configurations
This chapter includes feature-by-feature configuration procedures for the Cisco 806 router. This chapter is useful if you have a network in place and you want to add specific features.
If you prefer to use network scenarios to build a network, see Chapter 2, "Network Scenarios."
This chapter contains the following sections:
•
Before You Configure Your Network
•
Configuring Basic Parameters
•
Configuring Bridging
•
Configuring Routing
•
Configuring PPPoE Support
•
Configuring Network Address Translation
•
Configuring Dynamic Host Configuration Protocol
•
Configuring IP Multicasting
•
Configuring an Extended Access List
•
Configuring Network Time Protocol Support
•
Configuring IP Security and Generic Routing Encapsulation Tunneling
•
Configuring Other Security Features
•
Configuring Service Assurance Agent Support
Note
When you configure Ethernet interfaces, be aware that Ethernet 0 is the interface for hubbed ETHERNET ports 1 through 4, which support the local area network (LAN) on the premises, and Ethernet 1 is the interface for the INTERNET ETHERNET port.
Before You Configure Your Network
Before you configure your network, you must do the following:
•
Arrange for a digital subscriber line (DSL), cable, or Ethernet connection with your service provider.
•
If you are setting up an Internet connection, gather the following information:
–
Point-to-Point Protocol (PPP) client name that is assigned as your login name
–
PPP authentication type—Challenge Handshake Authentication Protocol (CHAP) or Password Authentication Protocol (PAP)
–
PPP password for accessing your Internet service provider (ISP) account
–
Domain Name System (DNS) server IP address and default gateways
•
If you are setting up a connection to a corporate network, you and its network administrator must generate and share the following information for the WAN interfaces of the routers:
–
PPP authentication type—CHAP or PAP
–
PPP client name for accessing the router
–
PPP password for accessing the router
•
If you are setting up Internet Protocol (IP) routing, generate the addressing scheme for your IP network.
Configuring Basic Parameters
To configure the router, perform the tasks described in the following sections:
•
Configuring Global Parameters
•
Configuring the Ethernet Interfaces
•
Configuring a Console Line for the Router
After your router boots, the following prompt displays. Enter no.
Would you like to enter the initial configuration dialog [yes]: no
For complete information on how to access global configuration mode, see the "Entering Global Configuration Mode" section in Appendix A, "Cisco IOS Basic Skills."
Configuring Global Parameters
Perform the following steps to configure the router for global parameters:
| |
Command
|
Task
|
Step 1
|
configure terminal
|
Enter configuration mode.
|
Step 2
|
hostname name
|
Specify the name for the router.
|
Step 3
|
enable secret password
|
Specify an encrypted password to prevent unauthorized access to the router.
|
Step 4
|
ip subnet-zero
|
Configure the router to recognize the zero subnet range as the valid range of addresses.
|
Step 5
|
no ip domain-lookup
|
Disable the router from interpreting unfamiliar words (typographical errors) entered during a console session as host names.
|
For complete information on the global parameter commands, refer to the Cisco IOS Release 12.0 documentation set.
Configuring the Ethernet Interfaces
To configure the Ethernet interfaces, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
interface ethernet 0
|
Enter configuration mode for the Ethernet 0 interface.
|
Step 2
|
ip address ip-address mask
|
Set the IP address and subnet mask for the Ethernet 0 interface.
|
Step 3
|
no shutdown
|
Enable the Ethernet 0 interface to change the state from administratively down to up.
|
Step 4
|
exit
|
Exit configuration mode for the Ethernet 0 interface.
|
Step 5
|
interface ethernet 1
|
Enter configuration mode for the Ethernet 1 interface.
|
Step 6
|
ip address ip-address mask
|
Set the IP address and subnet mask for the Ethernet 1 interface.
|
Step 7
|
no shutdown
|
Enable the Ethernet 1 interface to change the state from administratively down to up.
|
Step 8
|
end
|
Exit router configuration mode.
|
For complete information on the Ethernet commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on Ethernet concepts, see "Concepts."
Configuration Example
The following example shows the Ethernet interface configuration. You do not need to enter the commands marked "default." These commands appear automatically in the configuration file that is generated when you use the show running-config command.
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast (default)
ip address 192.168.2.1 255.255.255.0
no ip directed-broadcast (default)
Verifying Your Configuration
To verify that you have properly configured the Ethernet interface, enter the show interface ethernet 0 command and the show interface ethernet 1 command. You should see a verification output like the following examples:
router#show interface ethernet 0
Ethernet0 is up, line protocol is up
Hardware is PQUICC Ethernet, address is 00ff.ff20.008e
Internet address is 192.168.1.1/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
router#show interface ethernet 1
Ethernet1 is up, line protocol is up
Hardware is PQUICC_FEC, address is 00ff.ff20.008f
Internet address is 192.168.2.1/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Configuring a Console Line for the Router
To configure a console line that you can use to access the router over the network, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
line console 0
|
Enter line configuration mode, and specify the console terminal line.
|
Step 2
|
password password
|
Specify a unique password on the line.
|
Step 3
|
login
|
Enable password checking at terminal session login.
|
Step 4
|
exec-timeout 10 0
|
Set the interval that EXEC command interpreter waits until user input is detected. Exec-timeout 10 0 is the default.
|
Step 5
|
line vty 0 4
|
Specify a virtual terminal for remote console access.
|
Step 6
|
transport input ssh
|
This step is optional. Specify that only Secure Shell (SSH) be used for interactive logins to the router.
|
Step 7
|
password password
|
Specify a unique password on the line.
|
Step 8
|
login
|
Enable password checking at virtual terminal session login.
|
Step 9
|
end
|
Exit line configuration mode, and return to privileged EXEC mode.
|
For complete information on the command line commands, refer to the Cisco IOS Release 12.0 documentation set.
Configuration Example
The following configuration shows the command-line access commands.
You do not need to input the commands marked "default." These commands appear automatically in the configuration file that is generated when you use the show running-config command.
transport input none (default)
Verifying Your Configuration
You can verify your configuration by entering the show line console 0 command. The following example shows partial output from this command.
router#show line console 0
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise
Overruns Int
* 0 CTY - - - - - 0 1 0/0
-
Line 0, Location: "", Type: ""
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600, no parity, 1 stopbits, 8 databits...
Configuring Bridging
Bridges are store-and-forward devices that use unique hardware addresses to filter traffic that would otherwise travel from one segment to another. You can configure the Cisco 806 router as a pure bridge.
To configure bridging, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
no ip routing
|
Disable IP routing.
|
Step 2
|
bridge number protocol protocol
|
Specify the bridge protocol to define the type of Spanning-Tree Protocol (STP).
|
Step 3
|
interface ethernet 0
|
Enter configuration mode for the Ethernet 0 interface.
|
Step 4
|
bridge-group number
|
Specify the bridge-group number to which the Ethernet 0 interface belongs.
|
Step 5
|
no shutdown
|
Enable the Ethernet 0 interface.
|
Step 6
|
exit
|
Exit configuration mode for the Ethernet 0 interface.
|
Step 7
|
interface ethernet 1
|
Enter configuration mode for the Ethernet 1 interface.
|
Step 8
|
bridge-group number
|
Specify the bridge-group number to which the Ethernet 1 interface belongs.
|
Step 9
|
no shutdown
|
Enable the Ethernet 1 interface.
|
Step 10
|
end
|
Exit router configuration mode.
|
For complete information on the bridging commands, refer to the Cisco IOS Release 12.0 documentation set. For more general concepts on bridging, see "Concepts."
Configuration Example
The following configuration example uses bridging. You do not need to enter the commands marked "default." These commands appear automatically in the configuration file that is generated when you use the show running-config command.
This configuration example shows the Ethernet 0 and Ethernet 1 interfaces configured. The Ethernet interface has IP addressing turned off for bridging, and IP-directed broadcast is disabled, which prevents the translation of directed broadcasts to physical broadcasts. The bridge-group number with which the Ethernet 1 interface is associated is set to 1. The bridge protocol is set to 1 to define the STP.
no ip directed-broadcast (default)
no ip directed-broadcast (default)
Verifying Your Configuration
To verify that you have properly configured bridging, enter the show spanning-tree command. You should see a verification output similar to the following example:
router#show spanning-tree
Bridge group 1 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, address 00ff.ff20.008e
Configured hello time 2, max age 20, forward delay 15
Current root has priority 32768, address 00d0.d373.2ec0
Root port is 2 (Ethernet0), cost of root path is 200
Topology change flag not set, detected flag not set
Number of topology changes 1 last change occurred 00:00:38 ago
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers:hello 0, topology change 0, notification 0, aging 300
Port 2 (Ethernet0) of Bridge group 1 is forwarding
Port path cost 100, Port priority 128, Port Identifier 128.2.
Designated root has priority 32768, address 00d0.d373.2ec0
Designated bridge has priority 32768, address 00e0.1e58.8af2
Designated port id is 128.4, designated path cost 100
Timers:message age 2, forward delay 0, hold 0
Number of transitions to forwarding state:1
Port 3 (Ethernet1) of Bridge group 1 is forwarding
Port path cost 100, Port priority 128, Port Identifier 128.3.
Designated root has priority 32768, address 00d0.d373.2ec0
Designated bridge has priority 32768, address 00ff.ff20.008e
Designated port id is 128.3, designated path cost 200
Timers:message age 0, forward delay 0, hold 0
Number of transitions to forwarding state:1
Configuring Routing
This section provides instructions on configuring static, dynamic, and policy-based routing (PBR).
Configuring Static Routing
Static routes are routing information that you manually configure into the router. If the network topology changes, the static route must be updated with a new route. Static routes are private routes, unless they are redistributed by a routing protocol. It is optional to configure static routing on the Cisco 806 router.
To configure static routing, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
ip classless
|
Set up a best route for packets destined for networks unknown by the router.
|
Step 2
|
ip route network-number mask interface
|
Specify the static route for the IP packets.
|
Step 3
|
end
|
Exit router configuration mode.
|
For complete information on the static routing commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on static routing, see "Concepts."
Configuration Example
In the following configuration example, the static route is defined as a default route through the Dialer 0 interface. You would define a default static route through the Dialer interface when using PPPoE. You do not need to enter the commands marked "default." These commands appear automatically in the configuration file that is generated when you use the show running-config command.
ip route 0.0.0.0 0.0.0.0 dialer0
Verifying Your Configuration
To verify that you have properly configured static routing, enter the show ip route command, and look for static routes, indicated by the "S." You should see a verification output similar to the following example:
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is 0.0.0.0 to network 0.0.0.0
192.168.89.0/32 is subnetted, 2 subnets
10.0.0.0/24 is subnetted, 1 subnets
C 10.10.10.0 is directly connected, Ethernet0
S* 0.0.0.0/0 is directly connected, Dialer0
Configuring Dynamic Routing
In dynamic routing, the network protocol adjusts the path automatically, based on network traffic or topology. Changes in dynamic routing are shared with other routers in the network.
The IP routing protocol can use Routing Information Protocol (RIP) or Enhanced Interior Gateway Routing Protocol (IGRP) to learn routes dynamically. You can configure either of these routing protocols.
Configuring RIP
To configure RIP routing protocol on the router, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
ip routing
|
Enable IP routing.
|
Step 2
|
router rip
|
Enter router configuration mode, and enable RIP on the router.
|
Step 3
|
version 2
|
Specify use of RIP Version 2.
|
Step 4
|
network network-number
|
Specify the network number for each directly connected network.
|
Step 5
|
no auto-summary
|
Disable automatic summarization of subnet routes into network-level routes. This allows subprefix routing information to transmit across classful network boundries.
|
Step 6
|
end
|
Exit router configuration mode.
|
For complete information on the dynamic routing commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on RIP, see "Concepts."
Configuration Example
The following configuration shows RIP Version 2 enabled in IP network 10.10.10.0.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file that is generated when you use the show running-config command.
Verifying Your Configuration
To verify that you have properly configured RIP, enter the show ip route command, and look for RIP routes, indicated by the "R." You should see a verification output similar to the following example:
Codes:C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
10.0.0.0/24 is subnetted, 1 subnets
C 10.10.10.0 is directly connected, Ethernet0/0
R 3.0.0.0/8 [120/1] via 10.10.10.1, 00:00:02, Ethernet0/0
Configuring IP Enhanced IGRP
To configure IP Enhanced IGRP, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
ip routing
|
Enable IP routing.
|
Step 2
|
router eigrp autonomous-system
|
Enter router configuration mode, and enable Enhanced IGRP on the router. The autonomous-system number identifies the route to other Enhanced IGRP routers and is used to tag the Enhanced IGRP information.
|
Step 3
|
network network-number
|
Specify the network number for each directly connected network.
|
Step 4
|
end
|
Exit router configuration mode.
|
For complete information on the IP Enhanced IGRP commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on Enhanced IGRP concepts, see "Concepts."
Configuration Example
The following configuration shows Enhanced IGRP routing protocol enabled in IP network 10.10.10.0. The Enhanced IGRP autonomous system number is assigned as 100.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file that is generated when you use the show running-config command.
Verifying Your Configuration
To verify that you have properly configured IP Enhanced IGRP, enter the show ip route command, and look for Enhanced IGRP routes, indicated by "D." You should see a verification output similar to the following example:
Codes:C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
210.0.0.0/24 is subnetted, 1 subnets
C 10.10.10.0 is directly connected, Ethernet0/0
D 3.0.0.0/8 [90/409600] via 10.10.10.1, 00:00:02, Ethernet0/0
Configuring PBR
To configure PBR, you must complete the following tasks:
•
Create a route map that specifies the match criteria and the resulting action if all the match clauses are met. Then you must enable PBR for that route map on a particular interface.
•
Enable fast-switched PBR by invoking the ip route-cache policy command on the appropriate interface.
•
Enable local PBR if you want to policy route packets originating from the Cisco 806 router, by specifying a route map in global configuration mode.
For instructions on configuring PBR, refer to the Cisco IOS Release 12.0 Quality of Service Solutions Configuration Guide.
Configuring PPPoE Support
Configuring PPPoE support requires the creation of a VPDN, and changes to the Ethernet interfaces and the Dialer interface. To configure Point-to-Point Protocol over Ethernet (PPPoE) support, perform the following steps, beginning in global configuration mode. This procedure includes steps for configuring CHAP authentication. To configure PAP authentication, perform the steps in the following procedure to configure a VPDN and to configure the Ethernet 0 and the Ethernet 1 interface, but perform the steps in "Configuring PAP Authentication" to configure the Dialer interface.
| |
Command
|
Task
|
Step 1
|
vpdn enable
|
Configure the virtual private dial-up network.
|
Step 2
|
vpdn-group tag
|
Configure the VPDN group.
|
Step 3
|
request-dialin
|
Specify the dialing mode.
|
Step 4
|
protocol pppoe
|
Specify the PPPoE protocol for the VPDN group.
|
Step 5
|
interface ethernet 0
|
Configure the Ethernet 0 interface for PPPoe support.
|
Step 6
|
ip address ip-address subnet-mask
|
Set the IP address and subnet mask for the Ethernet 0 interface.
|
Step 7
|
ip tcp adjust-mss 1452
|
Specify the maximum segment size for TCP SYN packets.
|
Step 8
|
interface ethernet 1
|
Configure the Ethernet 1 interface for PPPoE support.
|
Step 9
|
no ip address
|
Disable IP addressing for the Ethernet 1 interface.
|
Step 10
|
pppoe enable
|
Enable the PPPoE protocol for the Ethernet 1 interface.
|
Step 11
|
pppoe-client dial-pool-number number
|
Configure a PPPoE client dial pool.
|
Step 12
|
exit
|
Exit Ethernet 1 interface configuration.
|
Step 13
|
interface dialer number
|
Configure the Dialer interface.
|
Step 14
|
ip address { negotiated | ip-address subnet-mask }
|
Indicate that the IP address is to be negotiated, or specify an IP address and subnet mask for the Dialer interface.
|
Step 15
|
ip mtu 1492
|
Set the size of the maximum IP transmission unit (MTU).
|
Step 16
|
encapsulation ppp
|
Specify the encapsulation type.
|
Step 17
|
dialer pool pool-number
|
Associate the dialer pool configured for the Ethernet 1 interface with the Dialer interface.
|
Step 18
|
dialer-group 1
|
Assign the Dialer interface to a dialer list.
|
Step 19
|
ppp authentication chap
|
Set the PPP authentication method. In this step, CHAP is specified. Alternatively, you can specify PAP.
|
Step 20
|
end
|
Exit router configuration.
|
Configuring PAP Authentication
If you need to use PAP authentication instead of CHAP, configure the VPDN and the Ethernet interfaces as shown in the previous procedure, but configure the Dialer interface by performing the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
interface dialer number
|
Configure the Dialer interface.
|
Step 2
|
ip address { negotiated | ip-address subnet-mask }
|
Indicate that the IP address is to be negotiated, or specify an IP address and subnet mask for the Dialer interface.
|
Step 3
|
ip mtu 1492
|
Set the size of the maximum IP transmission unit (MTU).
|
Step 4
|
encapsulation ppp
|
Specify the encapsulation type.
|
Step 5
|
dialer pool pool-number
|
Associate the dialer pool configured for the Ethernet 1 interface with the Dialer interface.
|
Step 6
|
dialer-group 1
|
Assign the Dialer interface to a dialer list.
|
Step 7
|
ppp authentication pap callin
|
Set the PPP authentication method to PAP, and indicate that the remote system is to be authenticated on incoming calls only.
|
Step 8
|
ppp pap sent-username username password password
|
Supply the PAP username and password.
|
Step 9
|
end
|
Exit router configuration mode.
|
Configuration Examples
The following example shows the VPDN configuration, and the Ethernet 0, Ethernet 1, and Dialer 0 interface configurations for PPPoE support. Use the show running-config command to view your configuration.
ip address 192.168.1.1 255.255.255.0
ip tcp adjust-mss 1452 (required for router to reach all websites)
pppoe-client dial-pool-number 1
The following example shows the Dialer configuration when the authentication type is PAP. The VPDN and Ethernet configurations would be the same as in the previous example.
ppp authentication pap callin
ppp pap sent-username sohodyne password 70703204E42081B
Verifying Your Configuration
To verify that you have properly configured PPPoE, enter the show ip interface dialer command. The verification output should be similar to the following sample. Not all output has been shown.
router#show ip interface dialer 0
Dialer1 is up, line protocol is up
Internet address is 192.168.89.109/32
Broadcast address is 255.255.255.255
Address determined by IPCP
Helper address is not set
Directed broadcast forwarding is disabled.....
Configuring Network Address Translation
This section describes how to configure addressing using Network Address Translation (NAT). You can configure NAT for static or dynamic address translations. It contains the following sections:
•
Configuring NAT
•
Configuring NAT with IPCP
Configuring NAT
To configure static or dynamic inside source translation using NAT, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
ip nat pool name start-ip end-ip { netmask netmask | prefix-length prefix-length}
|
Create a pool of global IP addresses for NAT.
|
Step 2
|
access-list access-list-number permit source [source-wildcard]
|
Define a standard access list permitting addresses that need translation.
|
Step 3
|
ip nat inside source list access-list-number pool name
|
Enable dynamic translation of addresses permitted by access list to one of the addresses specified in the pool.
|
Step 4
|
ip nat inside source static local-ip global-ip number extendable
|
Enable static translation of a specified inside local address to a globally unique IP address. This command is optional.
|
Step 5
|
interface ethernet 0
|
Enter configuration mode for the Ethernet 0 interface.
|
Step 6
|
ip nat inside
|
Establish the Ethernet 0 interface as the inside interface.
|
Step 7
|
exit
|
Exit configuration mode for the Ethernet 0 interface.
|
Step 8
|
interface ethernet 1
|
Enter configuration mode for the Ethernet 1 interface.
|
Step 9
|
ip nat outside
|
Establish the Ethernet 1 interface as the outside interface.
|
Step 10
|
end
|
Exit configuration mode for the Ethernet 1 interface and for the router.
|
For complete information on the NAT commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on NAT concepts, see "Concepts."
Configuration Example
The following configuration example shows NAT configured for the Ethernet 0 and Ethernet 1 interfaces.
The Ethernet 0 interface has an IP address of 192.168.1.1 and a subnet mask of 255.255.255.0. NAT is configured as inside, which means that the interface is connected to the inside network that is subject to NAT translation.
The Ethernet 1 interface has an IP address of 192.168.2.1 and a subnet mask of 255.255.255.0. NAT is configured as outside, which means that the interface is connected to an outside network, such as the Internet.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file that is generated when you use the show running-config command.
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast (default)
ip address 192.168.2.1 255.255.255.0
no ip directed-broadcast (default)
ip route 0.0.0.0 0.0.0.0 Ethernet1
ip nat pool homenet 192.168.2.1 192.168.2.1 netmask 255.255.255.0
ip nat inside source list 101 pool homenet overload
access-list 101 permit ip 192.168.1.0 0.0.0.255 any
Verifying Your Configuration
To verify that you have properly configured NAT, enter the show ip nat translation command. You should see a verification output similar to the following example:
router#show ip nat translation
Pro Inside global Inside local Outside local Outside global
tcp 192.168.1.1:2267 10.10.10.2:2267 63.148.48.18:80 192.168.2.1:80
utcp 192.168.1.1:2262 10.10.10.2:2262 207.69.188.186:53 192.168.2.1:53
udp 192.175.89.109:2266 10.10.10.2:2266 207.69.188.186:53 192.168.2.1:53
Configuring NAT with IPCP
This section explains how to configure NAT overload and PPP/Internet Protocol Control Protocol (IPCP). With NAT overload configured, you can use one registered IP address for the interface, and you can use it to access the Internet from all the devices in the network.
With PPP/IPCP, the Cisco 806 router automatically negotiates a globally unique (registered or public) IP address for the interface from the ISP route.
To configure NAT overload and IPCP, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
access-list access-list-number permit source [source-wildcard]
|
Define a standard access list that permits nonregistered IP addresses of hosts.
|
Step 2
|
ip nat inside source list access-list-number interface dialer 0 overload
|
Set up translation of addresses identified by the access list defined in Step 1.
|
Step 3
|
interface ethernet 0
|
Enter configuration mode for the Ethernet 0 interface.
|
Step 4
|
ip nat inside
|
Establish the Ethernet 0 interface as the inside interface for NAT.
|
Step 5
|
no shutdown
|
Enable the Ethernet 0 interface and the configuration changes you just made to it.
|
Step 6
|
exit
|
Exit configuration mode for the Ethernet 0 interface.
|
Step 7
|
interface dialer 0
|
Enter configuration mode for the Dialer 0 interface.
|
Step 8
|
ip address ip-address subnet-mask
|
Assign an IP address and subnet mask to the Dialer 0 interface.
|
Step 9
|
ip nat outside
|
Establish the Dialer 0 interface as the outside interface for NAT.
|
Step 10
|
end
|
Exit router configuration mode.
|
For complete information on these commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on NAT with IPCP concepts, see "Concepts."
Configuration Example
This configuration example shows the commands relevant to NAT with IPCP configurations. The access list configuration in this example will allow TCP applications such as FTP, Telnet, and HTTP, while blocking raw IP packets. The access list is applied to the Dialer 0 interface.
access-list 101 permit ip 192.168.1.0 0.255.255.255 any
ip nat inside source list 101 interface Dialer0 overload
ip address 192.168.1.1 255.255.255.0
pppoe-client dial-pool-number 1
ip address 140.10.10.5 255.255.255.0
Verifying Your Configuration
To verify that you have properly configured NAT, enter the show ip nat translation command. You should see a verification output similar to the following example:
router#show ip nat translation
Pro Inside global Inside local Outside local Outside global
tcp 192.168.1.1:2267 10.10.10.2:2267 63.148.48.18:80 192.168.2.1:80
utcp 192.168.1.1:2262 10.10.10.2:2262 207.69.188.186:53 192.168.2.1:53
udp 192.175.89.109:2266 10.10.10.2:2266 207.69.188.186:53 192.168.2.1:53
Configuring Dynamic Host Configuration Protocol
This section explains how to configure the Cisco 806 router for Dynamic Host Configuration Protocol (DHCP) support. It includes the following topics:
•
Configuring the DHCP Server and Relay
•
Configuring a DHCP Client
Configuring the DHCP Server and Relay
This section explains how to configure the Cisco 806 router as a DHCP server.
With DHCP, LAN devices on an IP network (DHCP clients) can request IP addresses from the DHCP server. The DHCP server allocates IP addresses from a central pool as needed. A DHCP server can be a workstation, a PC, or a Cisco router.
Configuring the DHCP Server
To configure the router as a DHCP server, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
ip dhcp pool name
|
Enter DHCP configuration mode, and create a pool of IP addresses that can be assigned to DHCP clients.
|
Step 2
|
network ip-address subnet-mask
|
Specify the network number and mask of the DHCP address pool.
|
Step 3
|
domain-name domain name
|
Configure the domain name.
|
Step 4
|
dns-server ip-address
|
Configure the DNS server.
|
Step 5
|
netbios-name-server ip-address
|
Configure the netbios name server.
|
Step 6
|
default-router ip-address
|
Designate a default router.
|
Step 7
|
lease { days | infinite }
|
Specify the duration of the lease by specifying the number of days the lease is to extend, or by indicating that the lease is not to expire.
|
Step 8
|
exit
|
Exit DHCP configuration mode.
|
For more information on the features not used in this configuration, refer to the Cisco IOS DHCP Server feature module. For more general information on DHCP servers, see "Concepts."
Configuration Example
The following example shows commands relevant to a DHCP server configuration. This DHCP server leases its addresses for 100 days.
network 10.10.10.0 255.255.255.0
default-router 10.10.10.20
netbios-name-server 10.10.10.40
Verifying Your Configuration
To verify that the server is assigning IP addresses to attached devices, use the show ip dhcp binding command on the DHCP server. You should see a verification output similar to the following example:
router#show ip dhcp binding
IP address Hardware address Lease expiration Type
10.10.10.2 0100.80c7.ecd6.70 Sep 02 2001 07:36 PM Automatic
Configuring the DHCP Relay
This section describes how to configure the router to forward User Datagram Protocol (UDP) broadcasts, including IP address requests, from DHCP clients. With the DHCP relay feature configured on the Cisco 806 router, the router can relay IP address requests from the LAN interface to the DHCP server.
To configure the DHCP relay, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
interface Ethernet 0
|
Enter configuration mode for the Ethernet 0 interface.
|
Step 2
|
ip helper-address address
|
Forward default UDP broadcasts, including IP configuration requests, to the DHCP server.
|
Step 3
|
no shutdown
|
Enable the Ethernet interface and the configuration changes.
|
Step 4
|
exit
|
Exit configuration mode for the Ethernet interface.
|
For complete information on the DHCP relay commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on DHCP relays, see "Concepts."
Configuration Example
The following configuration contains commands relevant to the DHCP relay only.
ip address 192.168.100.1 255.255.255.0
ip helper-address 200.200.200.1
Configuring a DHCP Client
If you do not configure PPPoE on the Cisco 806, you may wish to configure a DHCP client for the Ethernet 1 interface. Perform the following steps to configure the router for DHCP client support, starting in global configuration mode.
| |
Command
|
Task
|
Step 1
|
interface ethernet 1
|
Enter Ethernet 1 interface configuration.
|
Step 2
|
ip address dhcp
|
Specify that the Ethernet 1 interface is to receive its IP address from a DHCP server.
|
Step 3
|
end
|
Exit router configuration mode.
|
Configuration Example
The following configuration example shows the commands relevant to the Ethernet 1 interface. These command appear in the configuration file generated when you use the show running-config command.
Verifying Your Configuration
If the Cisco 806 router is a DHCP client, you can use the show dhcp lease command to determine the IP address the router is using, the subnet mask, the lease time, and other useful information.
You should see verification output similar to the following:
Temp IP addr: 188.188.1.40 for peer on Interface: Ethernet1
Temp sub net mask: 0.0.0.0
DHCP Lease server: 4.0.0.32, state: 3 Bound
DHCP transaction id: 2431
Lease: 3600 secs, Renewal: 1800 secs, Rebind: 3150 secs
Temp default-gateway addr: 188.188.1.1
Next timer fires after: 00:58:01
Retry count: 0 Client-ID: 0010.7b43.aa01
Configuring IP Multicasting
Configure multicast routing by completing the following tasks, starting in global configuration mode.
| |
Command
|
Task
|
Step 1
|
ip multicast-routing
|
Enable IP multicast forwarding.
|
Step 2
|
ip pim rp-address address
|
Configure the Protocol Independent Multicasting (PIM) Rendezvous Point (RP) address.
|
Step 3
|
interface ethernet 0
|
Enter Ethernet 0 interface configuration mode.
|
Step 4
|
ip address ip-address subnet-mask
|
Configure an IP address and subnet mask for the Ethernet 0 interface.
|
Step 5
|
ip pim { sparse | dense }-mode
|
Configure the Ethernet 0 interface for PIM sparse mode or PIM dense mode.
|
Step 6
|
interface dialer number
|
Enter Dialer interface configuration mode.
|
Step 7
|
ip address { ip-address subnet-mask | negotiated }
|
Specify an IP address and subnet mask for the Dialer interface, or indicate that the IP address is to be negotiated.
|
Step 8
|
ip pim { sparse | dense }-mode
|
Configure the Dialer interface for PIM sparse mode or PIM dense mode.
|
Step 9
|
end
|
Exit router configuration mode.
|
Configuration Example
The following example shows the relevant multicast-routing commands. The Ethernet 0 and the Dialer 0 interfaces have been configured for PIM sparse mode, and the PIM RP address has been defined as 192.168.20.3.
ip pim rp-address 192.168.20.3
ip address 192.168.1.1 255.255.255.0
ip address 140.10.10.5 255.255.255.0
Verifying Your Configuration
You can verify your configuration of multicasting by using the show ip igmp interface ethernet 0 command. You should see verification output similar to the following:
router#show ip igmp interface ethernet 0
Ethernet0 is up, line protocol is up
Internet address is 192.168.1.1/24
IGMP is enabled on interface
Current IGMP host version is 2
Current IGMP router version is 2
IGMP query interval is 60 seconds
IGMP querier timeout is 120 seconds
IGMP max query response time is 10 seconds
Last member query response interval is 1000 ms
Inbound IGMP access group is not set
IGMP activity:1 joins, 0 leaves
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 12.0.0.1 (this system)
IGMP querying router is 12.0.0.1 (this system)
Multicast groups joined (number of users):
Configuring an Extended Access List
To include one or more extended access lists in your router configuration, complete the following steps, beginning in global configuration mode.
Note
Extended access lists can be given tags consisting of numbers from 100 through 199, or they can be given alphanumeric tags. Alphanumeric tags must begin with a letter and must not contain any spaces.
| |
Command
|
Task
|
Step 1
|
access-list tag permit tcp any ip ip address-mask established
|
Permit any host on the network to access any Internet server.
|
Step 2
|
access-list tag deny ip ip adddress-mask any
|
Deny any Internet host from spoofing any host on the network.
|
Step 3
|
access-list tag permit tcp host ip address-mask
|
Permit the Internet DNS server to send TCP replies to any host on the network.
|
Step 4
|
access-list tag permit udp host ip address-mask
|
Permit the Internet DNS server to send UDP replies to any host on the network.
|
Step 5
|
access-list tag permit tcp any host ip address
|
Permit the Simple Mail Transfer Protocol (SMTP) mail server to access any Internet server.
|
Step 6
|
access-list tag permit tcp any host ip address
|
Permit the web server to access any Internet server.
|
Step 7
|
access-list tag permit icmp any any icmp-message-type
|
Permit ICMP messages of the specified type to be sent or received.
|
Step 8
|
access-list tag deny tcp any ip address-mask
|
Restrict any Internet host from making a Telnet connection to any host on the network.
|
Step 9
|
interface dialer number
|
Enter configuration mode for the Dialer interface.
|
Step 10
|
ip access-group tag in
|
Activate the access list of the specified tag.
|
Step 11
|
exit
|
Exit configuration mode for the Dialer interface.
|
For more complete information on the extended access list commands, refer to the Cisco IOS Release 12.0 documentation set. For information on TCP and UDP port assignments, see "Common Port Assignments."
Configuration Example
This configuration shows an access list being applied to IP address 198.92.32.130.
access-list 101 permit tcp any host 198.92.32.130 0.0.0.255
Verifying Your Configuration
Use the show access-lists command to verify access list configuration. The following example shows sample output for all access lists with the tag 101:
router> show access-lists 105
Extended IP access list 105
permit icmp any any echo-reply
permit icmp any any time-exceeded
permit icmp any any packet-too-big
permit icmp any any traceroute
permit icmp any any unreachable
deny ip host 255.255.255.255 any
deny ip 192.168.1.0 0.0.0.255 any
Configuring Network Time Protocol Support
The Network Time Protocol (NTP) is a protocol designed to time-synchronize a network of machines. NTP runs over UDP, which runs over IP. An NTP network usually gets its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server. NTP then distributes this time across the network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize two machines to within a millisecond of one another.
To identify a Network Time Protocol (NTP) server on the network and configure the Cisco 806 router as an NTP client, enter the following command in global configuration mode:
ntp server ip-address
where ip-address is the address of an NTP server on the network.
To configure the Cisco 806 router function as an NTP server, enter the following command in global configuration mode:
ntp master stratum-number
where stratum-number indicates the number of hops between the Cisco 806 router and an authorotative time source.
Configuring IP Security and Generic Routing Encapsulation Tunneling
IP Security (IPSec) provides secure tunnels between two peers, such as two routers. You define which packets are to be considered sensitive and thus should be sent through these secure tunnels. You also define the parameters which should be used to protect these sensitive packets, by specifying characteristics of these tunnels. Then, when the IPSec peer sees a sensitive packet, it sets up the appropriate secure tunnel and sends the packet through the tunnel to the remote peer.
The configuration of IPSec and GRE tunneling are presented together in this section. To configure IPSec using a GRE tunnel, perform the following steps, beginning in global configuration mode.
| |
Command
|
Task
|
Step 1
|
crypto isakmp policy 10
|
Define an Internet Key Exchange (IKE) policy, and assign the policy a priority. This command places the router in IKE policy configuration mode.
|
Step 2
|
hash md5
|
Specify the md5 hash algorithm for the policy.
|
Step 3
|
authentication pre-share
|
Specify pre-share key as the authentication method.
|
Step 4
|
exit
|
Exit IKE policy configuration mode.
|
Step 5
|
access-list 101 permit gre host starting-ip-address host ending-ip-address
|
Create an access list that permits the GRE protocol, and that specifies the IP addresses of the starting and ending points of the GRE tunnel.
|
Step 6
|
crypto isakmp key name address ip-address
|
Configure a pre-shared key and static IP address for each VPN client.
|
Step 7
|
crypto ipsec transform-set name esp-des esp-md5-hmac
|
Define a combination of security associations to occur during IPSec negotiations.
|
Step 8
|
crypto map name local-address ethernet 1
|
Enter crypto map configuration mode, and specify and name an identifying interface to be used by the crypto map for IPSec traffic.
|
Step 9
|
crypto map name seq-num ipsec-isakmp
|
Create a crypto map entry in IPSec ISAKMP mode, and enter crypto map configuration mode.
|
Step 10
|
set peer ip-address
|
Identify the remote IPSec peer.
|
Step 11
|
set transform-set name
|
Specify the transform set to be used.
|
Step 12
|
match address access-list-id
|
Specify an extended access list for the crypto map entry.
|
Step 13
|
exit
|
Exit crypto map configuration mode.
|
Step 14
|
interface ethernet 1
|
Configure the Ethernet 1 interface.
|
Step 15
|
ip address ip-address subnet-mask
|
Set the IP address and subnet mask for the Ethernet 1 interface.
|
Step 16
|
crypto map name
|
Associate the crypto map with the Ethernet 1 interface.
|
Step 17
|
exit
|
Exit Ethernet 1 interface configuration mode.
|
Step 18
|
interface tunnel 0
|
Configure the Tunnel 0 interface.
|
Step 19
|
ip address ip-address subnet-mask
|
Set the IP address and subnet mask for the Tunnel 0 interface.
|
Step 20
|
tunnel source ethernet 1
|
Specify the Ethernet 1 interface as the tunnel source.
|
Step 21
|
tunnel destination default-gwy-ip-address
|
Specify the default gateway as the tunnel destination.
|
Step 22
|
crypto map name
|
Associate the crypto map to the Tunnel 0 interface.
|
Step 23
|
end
|
Exit router configuration mode.
|
For more information on configuring IPSec and GRE tunneling, refer to the Cisco IOS Security Configuration Guide.
Configuration Example
The following configuration example shows the commands relevant to IPSec and and GRE tunneling. Note that the crypto map named mymap is associated with the Tunnel 0 interface and with the Ethernet 1 interface, and that the tunnel destination address of 140.10.10.6 matches the end point address in the access list.
crypto isakmp key cisco123 address 140.10.10.6
crypto ipsec transform-set myset esp-des esp-md5-hmac
crypto map mymap local-address Ethernet1
crypto map mymap 10 ipsec-isakmp
ip address 11.0.0.1 255.0.0.0
tunnel destination 140.10.10.6
ip address 140.10.10.5 255.255.255.0
access-list 101 permit gre host 140.10.10.5 host 140.10.10.6
Configuring Other Security Features
This section provides information about the security features available on the Cisco 806 router.
Configuring a RADIUS Client
Remote Authentication Dial-In User Service (RADIUS) enables you to secure your network agains unauthorized access. A RADIUS server must be configured in the service provider or corporate network in order for the Cisco 806 to use RADIUS client features.
To configure RADIUS on your Cisco 806 router, you must perform the following tasks:
•
Use the aaa new-model global configuration command to enable Authentication, Authorization, and Accounting (AAA). AAA must be configured if you plan to use RADIUS.
•
Use the aaa authentication global configuration command to define method lists for RADIUS authentication.
•
Use line and interface commands to enable the defined method lists to be used.
For instructions on configuring a RADIUS client, refer to the Cisco IOS Security Configuration Guide.
Configuring TACACS+
To configure your router to support TACACS+, you must perform the following tasks:
•
Use the aaa new-model global configuration command to enable AAA. AAA must be configured if you plan to use TACACS+.
•
Use the tacacs-server host command to specify the IP address of one or more TACACS+ daemons. Use the tacacs-server key command to specify an encryption key that will be used to encrypt all exchanges between the network access server and the TACACS+ daemon. This same key must also be configured on the TACACS+ daemon.
•
Use the aaa authentication global configuration command to define the method lists that use TACACS+ for authentication.
•
Use line and interface commands to apply the defined method lists to various interfaces.
You may need to perform other configuration steps if you need to enable accouting for TACACS+ connections. For instructions on configuring TACACS+, refer to the Security Configuration Guide.
Configuring Service Assurance Agent Support
The Cisco Service Assurance Agent (SA Agent) is an application-aware synthetic operation agent that monitors network performance by measuring key metrics such as response time, availability, jitter (interpacket delay variance), connect time, throughput, and packet loss. These metrics can be used for troubleshooting, for analysis for prevention of problems, and for designing future network topologies.
For instructions on configuring SA Agent support, refer to the Cisco IOS Release 12.0 documentation set.