<?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 Separate traffic by protocol - multiple internet interfaces in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/separate-traffic-by-protocol-multiple-internet-interfaces/m-p/1933939#M457175</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greg,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally you could use Policy based routing, but the ASA does not support this (yet), if you have a router in front of the ASA (so between the ISPs and your ASA), you could use PBR to split traffic between providers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check out this post:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/docs/DOC-6069"&gt;https://supportforums.cisco.com/docs/DOC-6069&lt;/A&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; it contains a discussion around using NAT to engineer what you are trying to achieve.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please rate if usefull.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dennis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Apr 2012 01:56:47 GMT</pubDate>
    <dc:creator>Dennis Mink</dc:creator>
    <dc:date>2012-04-11T01:56:47Z</dc:date>
    <item>
      <title>Separate traffic by protocol - multiple internet interfaces</title>
      <link>https://community.cisco.com/t5/network-security/separate-traffic-by-protocol-multiple-internet-interfaces/m-p/1933938#M457168</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to connect a second ISP link to our ASA 5510 to solely serve http traffic from our organization's employees (ie. web surfing). We currently have all employee traffic and two site-to-site VPN tunnels connecting to the internet from this firewall. I want to keep the tunnels as currently configured on the existing connection and split out http/https traffic from our staff onto a less costly link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How would I go about doing this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;BR /&gt;Greg&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:52:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/separate-traffic-by-protocol-multiple-internet-interfaces/m-p/1933938#M457168</guid>
      <dc:creator>gregbeifuss</dc:creator>
      <dc:date>2019-03-11T22:52:27Z</dc:date>
    </item>
    <item>
      <title>Separate traffic by protocol - multiple internet interfaces</title>
      <link>https://community.cisco.com/t5/network-security/separate-traffic-by-protocol-multiple-internet-interfaces/m-p/1933939#M457175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greg,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally you could use Policy based routing, but the ASA does not support this (yet), if you have a router in front of the ASA (so between the ISPs and your ASA), you could use PBR to split traffic between providers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check out this post:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/docs/DOC-6069"&gt;https://supportforums.cisco.com/docs/DOC-6069&lt;/A&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; it contains a discussion around using NAT to engineer what you are trying to achieve.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please rate if usefull.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dennis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Apr 2012 01:56:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/separate-traffic-by-protocol-multiple-internet-interfaces/m-p/1933939#M457175</guid>
      <dc:creator>Dennis Mink</dc:creator>
      <dc:date>2012-04-11T01:56:47Z</dc:date>
    </item>
  </channel>
</rss>

