04-06-2005 08:49 AM - edited 02-21-2020 01:42 PM
Does anyone know if an IOS based LNS can accept an empty (zero length) host name AVP? I get tunnel authorization fails when a LAC tries to connect.
Here is a brief debug output:
*Apr 6 09:20:41: L2TP: I SCCRQ from tnl 6465
*Apr 6 09:20:41: Tnl 63050 L2TP: Tunnel Authorization request failed.
*Apr 6 09:20:41: Tnl 63050 L2TP: Shutdown tunnel
*Apr 6 09:20:49: VPDN PROCESS From tunnel: Received 154 byte pak
*Apr 6 09:20:49: VPDN PROCESS From tunnel: Pak consumed
*Apr 6 09:20:49: L2X: Parse AVP 0, len 8, flag 0x8000 (M)
*Apr 6 09:20:49: L2X: Parse SCCRQ
*Apr 6 09:20:49: L2X: Parse AVP 2, len 8, flag 0x8000 (M)
*Apr 6 09:20:49: L2X: Protocol Ver 256
*Apr 6 09:20:49: L2X: Parse AVP 3, len 10, flag 0x8000 (M)
*Apr 6 09:20:49: L2X: Framing Cap 0x1
*Apr 6 09:20:49: L2X: Parse AVP 4, len 10, flag 0x8000 (M)
*Apr 6 09:20:49: L2X: Bearer Cap 0x1
*Apr 6 09:20:49: L2X: Parse AVP 5, len 14, flag 0x0
*Apr 6 09:20:49: L2X: Parse AVP 6, len 8, flag 0x0
*Apr 6 09:20:49: L2X: Firmware Ver 0x0
*Apr 6 09:20:49: L2X: Parse AVP 7, len 6, flag 0x8000 (M)
*Apr 6 09:20:49: L2X: Hostname
*Apr 6 09:20:49: L2X: Parse AVP 8, len 28, flag 0x0
*Apr 6 09:20:49: L2X: Vendor Name Nortel/Shasta Networks
*Apr 6 09:20:49: L2X: Parse AVP 9, len 8, flag 0x8000 (M)
*Apr 6 09:20:49: L2X: Assigned Tunnel ID 6465
*Apr 6 09:20:49: L2X: No missing AVPs in SCCRQ
*Apr 6 09:20:49: L2X: I SCCRQ, flg TLS, ver 2, len 112, tnl 0, ns 0, nr 0ter
contiguous pak, size 112
C8 02 00 70 00 00 00 00 00 00 00 00 80 08 00 00
00 00 00 01 80 08 00 00 00 02 01 00 80 0A 00 00
00 03 00 00 00 01 80 0A 00 00 00 04 00 00 00 01
00 0E 00 00 00 05 8B 5E 60 79 E1 38 DC 1E 00 08
00 00 00 06 00 00 80 06 ...
*Apr 6 09:20:49: L2TP: I SCCRQ from tnl 6465
*Apr 6 09:20:49: Tnl 58561 L2TP: Tunnel Authorization request failed.
*Apr 6 09:20:49: Tnl 58561 L2TP: Shutdown tunnelm no mon
04-12-2005 07:26 AM
It is not possible to enable authorization with an empty string because it will cause the tunnel authorization code to fail.
04-12-2005 08:26 AM
Authorization was off. Turned out to be an IOS bug. We downgraded from 12.3.11 to 12.3.6 and the problem went away.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide