Protocols and standards – H3C Technologies H3C SecPath F5020 User Manual
Page 37

29
Table 2 Tunnel attributes that can be issued by the RADIUS server
Attribute number
Attribute name
Description
64 Tunnel-Type
Tunnel type, which can only be L2TP.
65 Tunnel-Medium-Type
Transmission medium type for the tunnel, which can
only be IPv4.
67
Tunnel-Server-Endpoint
IP address of the LNS.
69
Tunnel-Password
Key used to authenticate a peer of the tunnel.
81 Tunnel-Private-Group-ID
Group ID for the tunnel.
The LAC sends this value to the LNS for the LNS to
perform an operation accordingly.
82 Tunnel-Assignment-ID
Assignment ID for the tunnel.
It is used to indicate the tunnel to which a session is
assigned. L2TP users with the same
Tunnel-Assignment-ID, Tunnel-Server-Endpoint, and
Tunnel-Password attributes share an L2TP tunnel.
The RADIUS server can issue only one set of the L2TP tunnel attributes in a RADIUS packet.
The RADIUS-issued tunnel attributes will override the tunnel attributes you have manually
configured on the LAC, but not vice versa.
•
L2TP tunnel switching—Also called multihop L2TP tunneling. As shown in
, the LTS device
terminates L2TP packets from each LAC as an LNS. It then sends these packets to a destination LNS
as an LAC.
L2TP tunnel switching has the following features:
{
Simplified configuration and deployment of LACs and LNSs in different management
domains—All LACs consider the LTS as an LNS, and do not need to differentiate LNSs on the
network. All LNSs consider the LTS as an LAC, and are not affected by the addition or deletion
of LACs.
{
L2TP tunnel sharing—Different users can share the same L2TP tunnel between the LAC and the
LTS. The LTS distributes data of different users to different LNSs.
Figure 13 L2TP tunnel switch network diagram
Protocols and standards
•
RFC 1661, The Point-to-Point Protocol (PPP)