Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

AnyConnect - metric/routing problems



During migrations from the old Cisco VPN cliënt to the AnyConnect cliënt, we run sometimes in routing problems. The old VPN-client provided, after connecting a VPN (splitt tunnel configuration) the routes of a higher metric than the metric of the local network. The local network (in case of overlap) will receive priority over the VPN route. This is normal and desirable behavior, as we expected. 

Now the problem with the Anyconnect client. AnyConnect has the ability to provide a low routing metric to the connected VPN networks. The result...The VPN traffic will always have priority over the routing of the local LAN. I know that the metric of the AnyConnect adapter can be modified. But it must be done with every new VPN connection. For our users, this is not a desirable situation.


Does anyone have any idea about this?


Please rate or mark answered for helpful posts.
CreatePlease to create content