【正文】 單擊【高級(jí)】進(jìn)入 圖 213 所示的窗口，進(jìn)入【L2TP 設(shè)置】選項(xiàng)卡，輸入隧道名稱 LAC，選擇認(rèn)證模式為 CHAP，單。單擊【下一步】 ，進(jìn)入 圖 211 所示窗口，在【連接名】處輸入一個(gè)連接名稱，例如“我的VPN 連接” ，在【登錄用戶名】處輸入用戶名，在【登錄密碼】處輸入密碼。單擊【下一步】 ，進(jìn)入 圖 29 所示窗口，單擊選定【L2TP IPSec VPN 協(xié)議】 。注意：要使 iNode 客戶端支持 L2TP 功能，在安裝過(guò)程中必須確認(rèn)安裝虛擬網(wǎng)卡（Virtual NIC） 。[RTAGigabitEther0/0]undo pppoeserver bindAll PPPoE Sessions on GigabitEther0/0 will be deleted, continue?[Y/N]:y [RTA]undo domain [RTA]undo l2tp enable[RTA]undo l2tpgroup 1[RTA]undo interface VirtualTemplate 0[RTA]undo localuser vpdnuser[RTA]undo domain 在 RTA、RTB 和 SWA 上配置 OSPF：[RTA]ospf[RTAospf1]area 0[]work []work [SWA]ospf[SWAospf1]area 0[]work []work [RTB]ospf[RTBospf1]area 0[]work 步驟三：安裝 iNode 客戶端在 PCA 上安裝 iNode 客戶端。實(shí)驗(yàn)任務(wù)二：配置客戶 LAC 模式步驟一：執(zhí)行基本配置步驟二：配置公網(wǎng)路由刪除所有靜態(tài)路由。RTAdebugging l2tp eventRTAdebugging l2tp controlRTBdebugging l2tp eventRTBdebugging l2tp control重新發(fā)起呼叫，通過(guò) debugging 信息觀察隧道建立的過(guò)程： RTA%Jun 29 16:10:23:450 2022 RTA IFNET/4/UPDOWN: Line protocol on the interface VirtualTemplate0:0 is UP *Jun 29 16:10:23:453 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: LAC is establishing a call on interface: VirtualTemplate0:0*Jun 29 16:10:23:454 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: Handle call UP, IfIndex =3145728*Jun 29 16:10:23:454 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: LNS address in RADIUS = *Jun 29 16:10:23:454 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: VPDN group number in RADIUS = 1*Jun 29 16:10:23:454 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: LNS address = *Jun 29 16:10:23:454 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: Add new call 11564 to tunnel 1 call list (total 1)*Jun 29 16:10:23:454 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: Get UDP port number successfully: port 1701*Jun 29 16:10:23:454 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Message Type: START_CONTROL_CONNECTION_REQUEST*Jun 29 16:10:23:598 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Protocol version: 100*Jun 29 16:10:23:699 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Host name: LAC*Jun 29 16:10:23:799 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Vendor name: H3C*Jun 29 16:10:23:910 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Framing capability :3*Jun 29 16:10:24:11 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Assigned Tunnel ID: 1*Jun 29 16:10:24:61 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Receive window size: 128*Jun 29 16:10:24:212 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Challenge :59 1A BB 52 70 E2 15 CD 82 C2 CC 3F 49 2F AB D4 *Jun 29 16:10:24:313 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Tunnel 1 started the Hello timer (60 seconds)*Jun 29 16:10:24:414 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Tunnel 1 sent a SCCRQ message*Jun 29 16:10:24:515 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Tunnel 1 recv ctrl message and restarted Hello timer*Jun 29 16:10:24:615 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: Received message type: 2*Jun 29 16:10:24:666 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: Board 0 recv from SOCK call ID=0 tunnel ID=1 MsgType = 2 Length = 117*Jun 29 16:10:24:767 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Proc a control message from the peer: type=2, len = 117*Jun 29 16:10:24:878 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Tunnel 1 recv SCCRP when in state 2*Jun 29 16:10:24:978 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Tunnel 1 started the Hello timer (60 seconds)*Jun 29 16:10:25:79 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Checked SCCRP MSG TYPE = 2*Jun 29 16:10:25:230 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Parse AVP Protocol version, value: 100*Jun 29 16:10:25:281 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Parse AVP Framing capability, value: 3*Jun 29 16:10:25:432 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Parse AVP Host name, value: LNS*Jun 29 16:10:25:532 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Parse AVP Remote tunnel ID: 1*Jun 29 16:10:25:633 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Parse AVP Bearer capability, value: .. . . ..學(xué)習(xí)參考3*Jun 29 16:10:25:784 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Parse AVP Receive window size: 128*Jun 29 16:10:25:885 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Parse AVP Challenge, Value: 81 14 35 54 9E DC AA 1D 55 3F 1D CA 6D 7F 51 AE *Jun 29 16:10:25:996 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Parse AVP Challenge response: 9F 97 EC A2 E6 84 68 56 77 FD EC 56 74 9A 6B 5D *Jun 29 16:10:26:46 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Message Type: START_CONTROL_CONNECTION_CONNECTED*Jun 29 16:10:26:147 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Challenge response:1D B5 3C B0 3C 23 C7 16 BC 70 76 22 2F F2 D3 2F *Jun 29 16:10:26:248 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Tunnel 1 sent SCCCN to tunnel 1*Jun 29 16:10:26:349 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Tunnel 1: waiting for calls*Jun 29 16:10:26:449 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Message Type: INCOMING_CALL_REQUEST*Jun 29 16:10:26:550 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Assigned call ID: 11564*Jun 29 16:10:26:651 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Call serial number: 11564*Jun 29 16:10:26:802 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Bearer type : 3*Jun 29 16:10:26:953 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Physical channel number: 0*Jun 29 16:10:27:64 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Put AVP Dialed number: 8888*Jun 29 16:10:27:215 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Call 11564 sent a ICRQ message*Jun 29 16:10:27:316 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Tunnel 1 recv ctrl message and restarted Hello timer*Jun 29 16:10:27:417 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: Received message type: 11*Jun 29 16:10:27:517 2022 RTA L2TP/7/L2TDBG: L2TP_EVENT: Board 0 recv from SOCK call ID=11564 tunnel ID=1 MsgType = 11 Length = 28*Jun 29 16:10:27:618 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Proc a control message from the peer: type=11, len = 28*Jun 29 16:10:27:719 2022 RTA L2TP/7/L2TDBG: L2TP_CONTROL: Ca