<?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 Thank you! It works but i don in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805368#M173026</link>
    <description>&lt;P&gt;Thank you! It works but i don't understand...&lt;/P&gt;
&lt;P&gt;Could you explain it? Why does it work?&lt;/P&gt;
&lt;P&gt;'sh route' shows only ome default route through ISP_1&lt;/P&gt;</description>
    <pubDate>Thu, 28 Jan 2016 09:02:58 GMT</pubDate>
    <dc:creator>lyutov_dv</dc:creator>
    <dc:date>2016-01-28T09:02:58Z</dc:date>
    <item>
      <title>PBR and Static NAT (Cisco ASA)</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805363#M173021</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;
&lt;P&gt;I have a problem with working PBR and Static NAT together on ASA.&lt;/P&gt;
&lt;P&gt;I have two ISP. I use the first one to provide internet access for users. The second one i want to use to publish SMTP server. I need to use PBR to make it work.&lt;/P&gt;
&lt;P&gt;I configured Static NAT and ACL to publish SMTP server.&lt;/P&gt;
&lt;P&gt;To provide routing I use PBR, because default route uses ISP_1.&lt;/P&gt;
&lt;P&gt;I created ACL to match traffic from SMTP server and to set default next hop.&lt;/P&gt;
&lt;P&gt;If SMTP server open a connection to any external server everything works good (traffic goes through ISP_2)&lt;/P&gt;
&lt;P&gt;But when i try to connect from test server in Internet it doesn't work... But when i configure static route to inside server through ISP_2 everything works great (it means ACL and NAT work correctly).&lt;/P&gt;
&lt;P&gt;I think this problem because ASA can't match traffic when an external server establishes a connection. (works stateful inspection). But i'm not sure and i don't know how to fix it.&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/media/dokument3.png" class="migrated-markup-image" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:11:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805363#M173021</guid>
      <dc:creator>lyutov_dv</dc:creator>
      <dc:date>2019-03-12T07:11:59Z</dc:date>
    </item>
    <item>
      <title>HI</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805364#M173022</link>
      <description>&lt;P&gt;HI&lt;/P&gt;
&lt;P&gt;Is it possible if you can share the configuration&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Jagmeet.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 01:35:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805364#M173022</guid>
      <dc:creator>jagmeesi</dc:creator>
      <dc:date>2016-01-28T01:35:52Z</dc:date>
    </item>
    <item>
      <title>Hi. My configuration is too</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805365#M173023</link>
      <description>&lt;P&gt;Hi. My configuration is too big because it working ASA and i wouldn't share the whole one.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But I can share certain partitions... Which one would you like to see?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I'm not sure only about PBR, because with the static route everything is OK.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 01:49:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805365#M173023</guid>
      <dc:creator>lyutov_dv</dc:creator>
      <dc:date>2016-01-28T01:49:19Z</dc:date>
    </item>
    <item>
      <title>show run nat</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805366#M173024</link>
      <description>&lt;P&gt;show run nat&lt;/P&gt;
&lt;P&gt;show run route-map&lt;/P&gt;
&lt;P&gt;show run interface&lt;/P&gt;
&lt;P&gt;show route&lt;/P&gt;
&lt;P&gt;show run route&lt;/P&gt;
&lt;P&gt;show run track&lt;/P&gt;
&lt;P&gt;show run access-list&lt;/P&gt;
&lt;P&gt;show run access-group&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Jagmeet.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 08:24:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805366#M173024</guid>
      <dc:creator>jagmeesi</dc:creator>
      <dc:date>2016-01-28T08:24:08Z</dc:date>
    </item>
    <item>
      <title>try this</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805367#M173025</link>
      <description>&lt;P&gt;try this&lt;/P&gt;
&lt;P&gt;Create a default route with higher Admin Distance&lt;/P&gt;
&lt;P&gt;Route ISP_2 0.0.0.0 0.0.0.0 &amp;lt;default gateway&amp;gt; 10&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Let me know if this works ?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Syed&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 08:45:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805367#M173025</guid>
      <dc:creator>Syed Taukir</dc:creator>
      <dc:date>2016-01-28T08:45:26Z</dc:date>
    </item>
    <item>
      <title>Thank you! It works but i don</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805368#M173026</link>
      <description>&lt;P&gt;Thank you! It works but i don't understand...&lt;/P&gt;
&lt;P&gt;Could you explain it? Why does it work?&lt;/P&gt;
&lt;P&gt;'sh route' shows only ome default route through ISP_1&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 09:02:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805368#M173026</guid>
      <dc:creator>lyutov_dv</dc:creator>
      <dc:date>2016-01-28T09:02:58Z</dc:date>
    </item>
    <item>
      <title>A very good question and it</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805369#M173027</link>
      <description>&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;A very good question and it helps increase our understanding about the FW.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;The reason why it has worked is because firewall does stateful inspection and builds connection whereas router doesn't do that.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;When traffic comes from ISP_2 to the Server on the DMZ, a connection is trying to be formed from ISP_2 to the&amp;nbsp;DMZ, the forward traffic is sent to the DMZ and the return path should also be via&amp;nbsp;the same interface (ISP_2) and not ISP_1.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;For the return traffic, the ASA looks at it's fast path "show asp table routing" and since there's no route via ISP_2, it drops the traffic.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;Now you would tell me&amp;nbsp;that the PBR is applied so the ASA should forward the traffic based on the policy-route. On the ASA, the PBR is applied on to the &lt;STRONG&gt;initial&lt;/STRONG&gt; packet and that's why when connection is initiated from DMZ it takes the ISP_2 but when the traffic is initiated from the ISP_2, the return path doesn't consult the policy-route.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new, courier, monospace"&gt;So when you applied the a route with higher AD "r&lt;/FONT&gt;&lt;FONT face="courier new, courier, monospace"&gt;&lt;SPAN&gt;oute ISP_2 0.0.0.0 0.0.0.0 &amp;lt;default gateway&amp;gt; 10" and if you check the &lt;STRONG&gt;ASP&lt;/STRONG&gt; routing table, the ASA now has a route via ISP_2 and without it, the ASA was dropping the traffic due to no route via ISP_2.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new, courier, monospace"&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;FONT face="courier new, courier, monospace"&gt;Reference&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new, courier, monospace"&gt;&lt;SPAN&gt;http://www.cisco.com/c/en/us&lt;/SPAN&gt;&lt;/FONT&gt;&lt;FONT face="courier new, courier, monospace"&gt;&lt;SPAN&gt;/td/docs/security/asa/asa82/configuration/guide/config/conns_tcpstatebypass.html&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new, courier, monospace"&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;HTH&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;Syed Taukir&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 20:51:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805369#M173027</guid>
      <dc:creator>Syed Taukir</dc:creator>
      <dc:date>2016-01-28T20:51:52Z</dc:date>
    </item>
    <item>
      <title>Thank you very much for your</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805370#M173028</link>
      <description>&lt;P&gt;Thank you very much for your explanation.&lt;/P&gt;
&lt;P&gt;I thought about stateful inspection but i had never heard about ASP before.&lt;/P&gt;
&lt;P&gt;It seems to be very useful for troubleshooting.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jan 2016 02:28:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805370#M173028</guid>
      <dc:creator>lyutov_dv</dc:creator>
      <dc:date>2016-01-29T02:28:31Z</dc:date>
    </item>
    <item>
      <title>Thank you very much, it realy</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805371#M173029</link>
      <description>&lt;P&gt;Thank you very much, it realy helped me! I have one OUTSIDE and two DMZ interfaces from another ISP with PBR default next hop policy. During a week, i tried do it using TCP state&lt;SPAN&gt;&amp;nbsp;bypass, but the solution is much simpler.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2016 13:30:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/2805371#M173029</guid>
      <dc:creator>Taras Manko</dc:creator>
      <dc:date>2016-02-13T13:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: A very good question and it</title>
      <link>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/3862980#M173030</link>
      <description>&lt;P&gt;Thank you for the explanation.&lt;/P&gt;&lt;P&gt;One question:&lt;/P&gt;&lt;P&gt;If the main ISP link goes down, will this second higher cost route not cause all the inside network devices to use the backup ISP?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(In our case, we are planning to link a second cellular 4G connection to the ASA to only route the voice vlan telephones and dont want all the users etc consume the limited bandwidth of the backup link. Any advise on this would be appreciated)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Deniz&lt;/P&gt;</description>
      <pubDate>Sun, 26 May 2019 16:30:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pbr-and-static-nat-cisco-asa/m-p/3862980#M173030</guid>
      <dc:creator>Deniz Miscioglu</dc:creator>
      <dc:date>2019-05-26T16:30:27Z</dc:date>
    </item>
  </channel>
</rss>

