<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic AnyConnect - metric/routing problems in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/anyconnect-metric-routing-problems/m-p/2557130#M236669</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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)&amp;nbsp;&lt;U&gt;the routes&lt;/U&gt; of a higher metric than the metric of the local network.&amp;nbsp;The local network (in case of overlap) will receive priority over the VPN route.&amp;nbsp;This is normal and desirable behavior, as we expected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;For our users, this is not a desirable situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have any idea about this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 04:27:09 GMT</pubDate>
    <dc:creator>Daniel Leonard</dc:creator>
    <dc:date>2019-03-12T04:27:09Z</dc:date>
    <item>
      <title>AnyConnect - metric/routing problems</title>
      <link>https://community.cisco.com/t5/network-security/anyconnect-metric-routing-problems/m-p/2557130#M236669</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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)&amp;nbsp;&lt;U&gt;the routes&lt;/U&gt; of a higher metric than the metric of the local network.&amp;nbsp;The local network (in case of overlap) will receive priority over the VPN route.&amp;nbsp;This is normal and desirable behavior, as we expected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;For our users, this is not a desirable situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have any idea about this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:27:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/anyconnect-metric-routing-problems/m-p/2557130#M236669</guid>
      <dc:creator>Daniel Leonard</dc:creator>
      <dc:date>2019-03-12T04:27:09Z</dc:date>
    </item>
  </channel>
</rss>

