 Feedback
|
Table Of Contents
Transparent Bridging Support for Authentication Proxy
Restrictions for Transparent Bridging Support for Authentication Proxy
Information About Transparent Bridging Support for Authentication Proxy
Benefits of Transparent Authentication Proxy
Transparent Authentication Proxy Overview
How to Configure Transparent Authentication Proxy
Configuration Examples for Transparent Authentication Proxy
Authentication Proxy in Transparent Bridge Mode: Example
Authentication Proxy in Concurrent Route Bridge Mode: Example
Authentication Proxy in Integrated Route Bridge Mode: Example
Feature Information for Transparent Authentication Proxy
Transparent Bridging Support for Authentication Proxy
First Published: June 29, 2007Last Updated: June 29, 2007The Transparent Bridging Support for Authentication Proxy feature allows network administrators to deploy authentication proxy on existing networks without changing the statically defined IP addresses of their network-connected devices. Thus, administrators can configure a security solution that dynamically authenticates and authorizes security polices on a per user basis.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Transparent Authentication Proxy" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS 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 Transparent Bridging Support for Authentication Proxy
•
•
•
•
Restrictions for Transparent Bridging Support for Authentication Proxy
Authentication Proxy is not supported on vLAN trunk interfaces that are configured in a bridge group.
Information About Transparent Bridging Support for Authentication Proxy
To use transparent authentication proxy in your network, you should understand the following concepts:
•
•
Benefits of Transparent Authentication Proxy
Added Security with Minimum Configuration
Users can simply configure transparent authentication proxy into an existing network without having to reconfigure their statically defined devices. Thus, the tedious and costly overhead that was required to renumber devices on the trusted network is eliminated.
Authentication Proxy on Bridged and Routed Interfaces
Authentication proxy rules on bridged interfaces can coexist with router interfaces on the same device, whenever applicable. Thus, users can deploy different authentication proxy rules on bridged and routed domains.
Transparent Authentication Proxy Overview
Authentication proxy provides dynamic, per-user authentication and authorization of network access connections. It allows network administrators to enforce security policies on per-user basis. Typically, authentication proxy is a Layer 3 functionality that is configured on routed interfaces with different networks and IP subnets on each interface.
Integrating authentication proxy with transparent bridging enables network administrators to deploy authentication proxy on an existing network without impacting the existing network configuration and IP address assignments of the hosts on the network.
Transparent Bridging Overview
If configured for bridging, a Cisco IOS device can bridge any number of interfaces. The device can complete basic bridging tasks such as learning MAC addresses on ports to restrict collision domains and running Spanning Tree Protocol (STP) to prevent looping in the topology.
Within bridging, a user can configure Integrated Routed Bridging (IRB), which allows a device to bridge on some interfaces while a Layer 3 Bridged Virtual Interface (BVI) is presented for routing. The bridge can determine whether the packet is to be bridged or routed on the basis of the destination of the Layer 2 or Layer 3 IP address in the packet. Configured with an IP address, the BVI can manage the device even if no interface is configured for routing.
How to Configure Transparent Authentication Proxy
To configure authentication proxy on bridged interfaces, you must configure the interface in a bridge group and apply an authentication proxy rule on the interface. You must also set up and configure the authentication, authorization, and accounting (AAA) server (Cisco ACS) for authentication proxy. For examples on how to configure authentication proxy on a bridged interface, see the section, "Configuration Examples for Transparent Authentication Proxy" section.
Configuration Examples for Transparent Authentication Proxy
This section contains the following configuration examples, which show how to configure authentication proxy on a bridged interface:
•
•
•
Authentication Proxy in Transparent Bridge Mode: Example
The following example (see Figure 1) shows how to configure authentication proxy in a transparent bridged environment in which network users (that is, hosts on the bridged interface FastEthernet 5/0) are challenged for user credentials before being given access to protected resources.
Figure 1 Authentication Proxy in Transparent Bridging Mode: Sample Topology
aaa new-model!aaa authentication login default group radiusaaa authorization auth-proxy default group radiusaaa accounting auth-proxy default start-stop group radius!no ip routing!!no ip cef!ip auth-proxy name AuthRule http inactivity-time 60!interface FastEthernet5/0ip address 10.0.0.2 255.255.255.0ip auth-proxy AuthRuleip access-group 100 inno ip route-cacheduplex autospeed autobridge-group 1!interface FastEthernet5/1no ip addressno ip route-cacheduplex autospeed autobridge-group 1!ip http serverip http secure-server!radius-server host 10.0.0.5 auth-port 1645 acct-port 1646radius-server key cisco!bridge 1 protocol ieee!Router# show ip auth-proxy cacheAuthentication Proxy CacheClient Name AuthRule, Client IP 10.0.0.1, Port 1100,timeout 60, Time Remaining 60, state ESTABAuthentication Proxy in Concurrent Route Bridge Mode: Example
Concurrent routing and bridging configuration mode allows routing and bridging to occur in the same router; however, the given protocol is not switched between the two domains. Instead, routed traffic is confined to the routed interfaces and bridged traffic is confined to the bridged interfaces.
The following example (see Figure 2) shows how to configure authentication proxy in a concurrent routing and bridging environment in which network users (that is, hosts on the bridged interface FastEthernet 5/0) are challenged for user credentials before being given access to protected resources.
Figure 2 Authentication Proxy in Concurrent Route Bridge Mode: Sample Topology
aaa new-model!aaa authentication login default group radiusaaa authorization auth-proxy default group radiusaaa accounting auth-proxy default start-stop group radiusb!ip cef!bridge crb!ip auth-proxy name AuthRule http inactivity-time 60!interface FastEthernet5/0ip address 10.0.0.2 255.255.255.0ip auth-proxy AuthRuleip access-group 100 inno ip route-cacheduplex autospeed autobridge-group 1!interface FastEthernet5/1no ip addressno ip route-cacheduplex autospeed autobridge-group 1!ip http serverip http secure-server!radius-server host 10.0.0.5 auth-port 1645 acct-port 1646radius-server key cisco!bridge 1 protocol ieee!Router# show ip auth-proxy cacheAuthentication Proxy CacheClient Name AuthRule, Client IP 10.0.0.1, Port 1145,timeout 60, Time Remaining 60, state ESTABAuthentication Proxy in Integrated Route Bridge Mode: Example
In an integrated routing and bridging environment, a bridged network is interconnected with a router network. Both routing and bridging can occur in the same router with connectivity between routed and bridged domains.
The following example (see Figure 3) shows how to configure authentication proxy in an integrated routing and bridging environment in which network users (that is, hosts on the bridged interface FastEthernet 5/0) are challenged for user credentials before being given access to protected resources.
Figure 3 Authentication Proxy in Integrated Route Bridge Mode: Sample Topology
!aaa new-model!aaa authentication login default group radiusaaa authorization auth-proxy default group radiusaaa accounting auth-proxy default start-stop group radius!ip cef!ip auth-proxy name AuthRule http inactivity-time 60!bridge irb!interface FastEthernet3/0no ip addressduplex halfbridge-group 1!interface FastEthernet5/0no ip addressip auth-proxy AuthRuleip access-group 100 induplex autospeed autobridge-group 1!interface FastEthernet5/1no ip addressduplex autospeed autobridge-group 1!interface BVI1ip address 10.0.0.25 255.255.255.0!!ip route 11.0.0.0 255.255.255.0 10.0.0.7!ip http serverip http secure-server!radius-server host 11.0.0.5 auth-port 1645 acct-port 1646radius-server key cisco!bridge 1 protocol ieeebridge 1 route ip!Router# show ip auth-proxy cacheAuthentication Proxy CacheClient Name AuthRule, Client IP 10.0.0.1, Port 1100,timeout 60, Time Remaining 60, state ESTABAdditional References
The following sections provide references related to the Transparent Bridging Support for Authentication Proxy feature.
Related Documents
Standards
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
Technical Assistance
Command Reference
This feature uses no new or modified commands.
Feature Information for Transparent Authentication Proxy
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS 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
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
