Добавил:
Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
Building And Integrating Virtual Private Networks With Openswan (2006).pdf
Скачиваний:
78
Добавлен:
17.08.2013
Размер:
4.74 Mб
Скачать

Debugging and Troubleshooting

Microsoft L2TP Errors

The following section summarizes common errors related to Windows and L2TP. The error message you might see is given, followed by an explanation of the cause and how to fix it.

chalresp_avp: Challenge reply found

control_finish: Invalid authentication for host 'XENU2005'

call_close : Connection 27 closed to 193.110.157.131, port 1701 (Invalid challenge authentication)

You have enabled L2TP authentication instead of PPP authentication. Windows does not support this mode of authentication. Remove the auth file and challenge parameters from l2tpd.conf.

Jun 29 03:34:18 aivd pppd[24014]: Connect: ppp0 <--> /dev/pts/1

Jun 29 03:34:20 aivd pppd[24014]: peer refused to authenticate: terminating link

Jun 29 03:34:26 aivd pppd[24014]: Connection terminated. Jun 29 03:34:27 aivd pppd[24014]: Exit.

Jun 29 03:34:27 aivd l2tpd[14785]: network_thread: tossing read packet, error= Bad file descriptor (9). Closing call.

Windows then shows the error:

Error 734: The PPP link control protocol was terminated

This tells you that there was a disagreement about the authentication method to use. For instance, you might have forgotten to change the L2TP encryption option on Windows from encryption required to encryption optional. Windows then insists on L2TP encryption, which l2tpd on Linux does not support, and does not need because IPsec already takes care of encryption. Another cause behind this could be if the Windows L2TP connection is configured to only use CHAP MS-v2, and you forgot to add regular CHAP, or you changed it back after the bogus Windows message about CHAP resulting in unencrypted connections. Change this in L2TP Properties | Security | Advanced Settings.

Error 732: The PPP negotiation is not converging

This usually means that you have specified an incorrect local IP in your l2tpd.options file. It should be the local (private) IP address of the Openswan server, not the public IP address.

Error 734: The PPP link control protocol terminated

This error happens when for some reason 'call back' is set on the Windows L2TP connection. Disable it by selecting the Networking tab and then open the Settings option in the properties window of your L2TP connection and disable LCP extensions.

Error 781: Encryption failed because no valid certificate was found

The X.590 Certificate was not properly imported, or does not work in combination with the Openswan server. Check your X.509 Certificate and CA certificate using the MMC, or use certimport.exe to re-import the certificates properly.

Error 789: The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer

274