
Configuring Dial Services
6-14
117353-B Rev. 00
RADIUS Authentication Services for Demand Circuit Groups
As networks grow to accommodate more remote users, network security and
billing become more difficult to manage. RADIUS is an Internet draft
specification that solves these issues by centralizing security and accounting
information. Centralizing these services improves security and provides a solution
that can adapt to the changing size and needs of the remote user and service
providers.
In a RADIUS application, there is a client and a server. The router is the RADIUS
client. You can only configure RADIUS authentication for incoming calls that use
unnumbered protocol interfaces in a demand circuit group configuration. Demand
circuit groups work well with RADIUS configurations because they simplify
configuration for large numbers of remote users. The unnumbered protocol
configuration enables the incoming call to use any available circuit, so many
remote users can place calls, even if their number exceeds the number of
configured circuits.
For detailed information about RADIUS, see Configuring RADIUS.
Managing Broadcast Traffic over Demand Circuits
Many of the routing protocols that you can select for a demand circuit send update
packets out to the network. Update packets maintain routing tables and gather
information about network resources. For dial-on-demand, the frequency of these
update packets forces the dial-up connection to remain activated (unless you
configure a time of day to deactivate it). When routers exchange update packets,
the physical connection is established, unless you create a filter.
To reduce this type of traffic, you can configure one of the following:
• Static routes
• Dial optimized routing
• RIP triggered updates and broadcast timers (for IP)
• RIP and SAP broadcast timers (for IPX)
• Traffic filters
Each method is described in the sections that follow.
Kommentare zu diesen Handbüchern