<?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 VPN QoS in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318968#M951330</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have c2600 router connected with ipsec VPN to ASA5520. I want to apply QoS on router, because link is congested by corporate regular traffic. I want to prioritize traffic communicating on ports 5061-5064 (voice, video...).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What can be the best QoS strategy for this scenario?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.  &lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 11:33:39 GMT</pubDate>
    <dc:creator>lubosbella</dc:creator>
    <dc:date>2020-02-21T11:33:39Z</dc:date>
    <item>
      <title>VPN QoS</title>
      <link>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318968#M951330</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have c2600 router connected with ipsec VPN to ASA5520. I want to apply QoS on router, because link is congested by corporate regular traffic. I want to prioritize traffic communicating on ports 5061-5064 (voice, video...).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What can be the best QoS strategy for this scenario?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.  &lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 11:33:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318968#M951330</guid>
      <dc:creator>lubosbella</dc:creator>
      <dc:date>2020-02-21T11:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: VPN QoS</title>
      <link>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318969#M951331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since you mention VPN, I'm assuming this is across the Internet?  If true, are the Internet links used by the VPN used by other than just this one VPN connection? If so, very difficult to impossible to guarantee service.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there's just the VPN connection across the Internet, I've found an effective QoS strategy to be to shape such that bandwidth bottlenecks are avoided except at the Internet endpoints, and for those, use CBWFQ to implement QoS to treat traffic as necessary (e.g. LLQ for real-time traffic such as VoIP).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not familar with the capabilities of the ASA.  What all the 2600 can do depends on the IOS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Jul 2009 12:22:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318969#M951331</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2009-07-11T12:22:18Z</dc:date>
    </item>
    <item>
      <title>Re: VPN QoS</title>
      <link>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318970#M951332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Like Joseph stated, if this goes over the internet, it's best effort. That being said, I have a client that was having this issue and as a test we gave priority to the remote end IP. It has resolved most of their VoIP issues over the VPN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map match-all VPN-CLASS&lt;/P&gt;&lt;P&gt; match access-group name VPN&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;policy-map QOS-POLICY&lt;/P&gt;&lt;P&gt; class VPN-CLASS&lt;/P&gt;&lt;P&gt;  priority 512&lt;/P&gt;&lt;P&gt; class class-default&lt;/P&gt;&lt;P&gt;  fair-queue&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;ip access-list extended VPN&lt;/P&gt;&lt;P&gt; permit ip host 68.115.x.y any&lt;/P&gt;&lt;P&gt; permit ip any host 68.115.x.y&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;interface s0/0/0&lt;/P&gt;&lt;P&gt; service-policy output VPN-POLICY &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Jul 2009 12:57:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318970#M951332</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-07-13T12:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: VPN QoS</title>
      <link>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318971#M951333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;maybe i should more specify conditions. In attachment is a scheme of my network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Im not sure if it is possible to use a CBWFQ strategy because congested router have only one physical interface divided into subinterfaces and CBWFQ method dont support it officialy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Collin your configuration is applied to ASA or C2600?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jul 2009 06:41:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318971#M951333</guid>
      <dc:creator>lubosbella</dc:creator>
      <dc:date>2009-07-14T06:41:21Z</dc:date>
    </item>
    <item>
      <title>Re: VPN QoS</title>
      <link>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318972#M951334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is from a 2811 running 12.4(5)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jul 2009 13:58:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-qos/m-p/1318972#M951334</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-07-14T13:58:27Z</dc:date>
    </item>
  </channel>
</rss>

