Please select To the mobile version | Continue to access the desktop computer version
 Forgot password?
 Register now


Router

View: 7836|Reply: 1

When an RSR Functions as an L2TP LNS, the Client Dial-up Fails. After the debug vpdn Command Is Executed on the LNS, the Prompt "ctrl pak can't find tunnel" Is Displayed.

[Copy link]

18

Digests

1011

Posts

1164

Credits

administrator

Rank: 9Rank: 9Rank: 9

Credits
1164
Post time 2017-5-4 19:32:41 | Show all posts |Read mode
When an RSR Functions as an L2TP LNS, the Client Dial-up Fails. After the debug vpdn Command Is Executed on the LNS, the Prompt "ctrl pak can't find tunnel" Is Displayed.
Reply

Use magic Report

18

Digests

1011

Posts

1164

Credits

administrator

Rank: 9Rank: 9Rank: 9

Credits
1164
 Author| Post time 2017-5-4 19:35:21 | Show all posts
*Apr 11 15:56:49: %7: L2TP: received 112 bytes data from UDP
*Apr 11 15:56:49: %7: L2TP: I SCCRQ from pdsn ip 115.168.101.149 sport 1701 rtnlid 146
*Apr 11 15:56:49: %7: L2TP: ctrl pak can't find tunnel

The debug information shows that the cause for the client dial-up failure is that a matched tunnel cannot be found locally, which is generally due to inconsistency between the peer identifierand the local identifier.

According to the preceding debug information, the peer identifier is PDSN. Check whether local identifier configured using the terminate-from hostname command is PDSN.

Reply Support Not support

Use magic Report

You have to log in before you can reply Login | Register now