-
- IP Access List Features Roadmap
- IP Access List Overview
- Creating an IP Access List and Applying It to an Interface
- Creating an IP Access List to Filter IP Options TCP Flags Noncontiguous Ports or TTL Values
- Refining an IP Access List
- Displaying and Clearing IP Access List Data Using ACL Manageability
- Controlling Access to a Virtual Terminal Line
- Access List-Based RBSCP
- ACL IP Options Selective Drop
- ACL Authentication of Incoming rsh and rcp Requests
- Configuring Lock-and-Key Security for Dynamic Access Lists
- Configuring IP Session Filtering of Reflexive Access Lists
- Configuring TCP Intercept and Preventing Denial-of-Service Attacks
-
- Configuring Context-based Access Control
- Application Firewall - Instant Message Traffic Enforcement
- Cisco IOS Firewall MIB
- Cisco IOS Firewall Performance Improvements
- Cisco IOS Firewall Stateful Failover
- Cisco IOS Firewall Support for TRP
- Email Inspection Engine
- ESMTP Support for Cisco IOS Firewall
- Firewall ACL Bypass
- Firewall N2H2 Support
- Firewall Stateful Inspection of ICMP
- Firewall Support for SIP
- Firewall Support of Skinny Client Control Protocol
- Firewall Websense URL Filtering
- Granular Protocol Inspection
- HTTP Inspection Engine
- Inspection of Router-Generated Traffic
- TCP Out-of-Order Packet Support for Cisco IOS Firewall and Cisco IOS IPS
- Transparent Cisco IOS Firewall
- Virtual Fragmentation Reassembly
- VRF Aware Cisco IOS Firewall
- Configuring Port to Application Mapping
- Configuring Cisco IOS Intrusion Prevention System (IPS)
- Configuring IP Security Options
- Finding Feature Information
- Contents
- Restrictions for Controlling Access to a Virtual Terminal Line
- Information About Controlling Access to a Virtual Terminal Line
- How to Control Access to a Virtual Terminal Line
- Configuration Examples for Controlling Access to a Virtual Terminal Line
- Where to Go Next
- Additional References
- Feature Information for Controlling Access to a Virtual Terminal Line
Controlling Access to a Virtual Terminal Line
You can control who can access the virtual terminal lines (vtys) to a router by applying an access list to inbound vtys. You can also control the destinations that the vtys from a router can reach by applying an access list to outbound vtys.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Controlling Access to a Virtual Terminal Line" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•Restrictions for Controlling Access to a Virtual Terminal Line
•Information About Controlling Access to a Virtual Terminal Line
•How to Control Access to a Virtual Terminal Line
•Configuration Examples for Controlling Access to a Virtual Terminal Line
•Feature Information for Controlling Access to a Virtual Terminal Line
Restrictions for Controlling Access to a Virtual Terminal Line
When you apply an access list to a vty (by using the access-class command), the access list must be a numbered access list, not a named access list.
Information About Controlling Access to a Virtual Terminal Line
•Benefits of Controlling Access to a Virtual Terminal Line
Benefits of Controlling Access to a Virtual Terminal Line
By applying an access list to an inbound vty, you can control who can access the lines to a router. By applying an access list to an outbound vty, you can control the destinations that the lines from a router can reach.
How to Control Access to a Virtual Terminal Line
•Controlling Inbound Access to a vty
•Controlling Outbound Access to a vty
Controlling Inbound Access to a vty
Perform this task when you want to control access to a vty coming into the router by using an access list. Access lists are very flexible; this task illustrates one access-list deny command and one access-list permit command. You will decide how many of each command you should use and their order to achieve the restrictions you want.
SUMMARY STEPS
1. enable
2. configure terminal
3. access-list access-list-number deny {source [source-wildcard] | any} [log]
4. access-list access-list-number permit {source [source-wildcard] | any} [log]
5. line vty line-number [ending-line-number]
6. access-class access-list-number in [vrf-also]
7. exit
8. Repeat Steps 5 and 6 for each line to set identical restrictions on all the virtual terminal lines because a user can connect to any of them.
9. end
10. show line [line-number | summary]
DETAILED STEPS
Controlling Outbound Access to a vty
Perform this task when you want to control access from a vty to a destination. Access lists are very flexible; this task illustrates one access-list deny command and one access-list permit command. You will decide how many of each command you should use and their order to achieve the restrictions you want.
When a standard access list is applied to a line with the access-class out command, the address specified in the access list is not a source address (as it is in an access list applied to an interface), but a destination address.
SUMMARY STEPS
1. enable
2. configure terminal
3. access-list access-list-number deny {destination [destination-wildcard] | any}[log]
4. access-list access-list-number permit {destination [destination-wildcard] | any}[log]
5. line vty line-number [ending-line-number]
6. access-class access-list-number out
7. exit
8. Repeat Steps 5 and 6 for each line to set identical restrictions on all the virtual terminal lines because a user can connect to any of them.
9. end
10. show line [line-number | summary]
DETAILED STEPS
Configuration Examples for Controlling Access to a Virtual Terminal Line
•Example: Controlling Inbound Access on vtys
•Example: Controlling Outbound Access on vtys
Example: Controlling Inbound Access on vtys
The following example defines an access list that permits only hosts on network 172.19.5.0 to connect to the virtual terminal lines 1 through 5 on the router. Because the vty keyword is omitted from the line command, the line numbers 1 through 5 are absolute line numbers.
access-list 12 permit 172.19.5.0 0.0.0.255
line 1 5
access-class 12 in
Example: Controlling Outbound Access on vtys
The following example defines an access list that denies connections to networks other than network 171.20.0.0 on terminal lines 1 through 5. Because the vty keyword is omitted from the line command, the line numbers 1 through 5 are absolute line numbers.
access-list 10 permit 172.20.0.0 0.0.255.255
line 1 5
access-class 10 out
Where to Go Next
You can further secure a vty by configuring a password with the password line configuration command. See the password (line configuration) command in the Cisco IOS Security Command Reference.
Additional References
Related Documents
|
|
---|---|
Cisco IOS commands |
|
Configuring a password on a line |
Standards
|
|
---|---|
None |
— |
MIBs
|
|
---|---|
None |
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
|
|
---|---|
None |
— |
Technical Assistance
Feature Information for Controlling Access to a Virtual Terminal Line
Table 1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2006 Cisco Systems, Inc. All rights reserved.