Previously, the client derived a rough estimate MTU which covered both TLS/DTLS and was obviously less than optimal.

This could be because of two reasons:Īs of ASA Release 9.x and An圜onnect Release 4.x, an optimization has been introduced in the form of distinct Maximum Transition Units (MTUs) that are negotiated for TLS/DTLS between the client/ASA. The cause of this issue is the failure to build a Datagram Transport Layer Security (DTLS) tunnel.

Private network may need to be restarted.

******************************************ĭescription : The entire VPN connection is being reconfigured.ĭescription : Message type information sent to the user:ĭescription : A new MTU needs to be applied to the VPN network interface.ĭisabling and re- enabling the Virtual Adapter. Transmitting large packet 1418 (threshold 1347). This syslog is seen on the ASA: %ASA-6-722036: Group User IP In this example, the An圜onnect client is shown as it reconnects to the ASA. This is dependent upon a few other factors which are discussed in this document. If An圜onnect client reconnects to the Adaptive Security Appliance (ASA) in exactly one minute, users cannot receive traffic over the Transport Layer Security (TLS) tunnel until An圜onnect reconnects. These products were effected by this problem: If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment.

This document is not restricted to specific software and hardware versions. There are no specific requirements for this document. This document describes what happens when an An圜onnect client reconnects to the Adaptive Security Appliance (ASA) in exactly one minute.

Anyconnect vpn not working