<?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 Hello Chris, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788201#M173326</link>
    <description>&lt;P&gt;Hello Chris,&lt;/P&gt;
&lt;P&gt;I opened a TAC case and we confirmed that configuration is correct so we started looking at the possibility of a bug with PBR feature.&amp;nbsp; We did find a bug logged that matches my problem but at the same time we realized we could get it working on the TAC agent's lab environment and also on a different system that I have access to.&amp;nbsp; Going further, I tested on a fourth system and was able to reproduce the bug/problem.&lt;/P&gt;
&lt;P&gt;The interesting thing is that the two systems that have the bug/problem use the same model Comcast modem&amp;nbsp;for the PBR next-hop target.&amp;nbsp; The two systems that work are a lab system and a&amp;nbsp;live system that uses a Cisco router as the PBR next-hop target.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So my gut feeling now tells me that there is something odd about the way the Comcast modem is handling the ASA packets that causes this bug/problem.&amp;nbsp; It would be interesting to find out if the previous guys who logged the bug/problem were also using Comcast or similar cable modem devices but I don't know if that is possible.&lt;/P&gt;
&lt;P&gt;In any case I am going to work with the TAC a bit more and see what we find.&amp;nbsp; I will update the post when we are done.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 27 Jan 2016 05:53:59 GMT</pubDate>
    <dc:creator>tato386</dc:creator>
    <dc:date>2016-01-27T05:53:59Z</dc:date>
    <item>
      <title>static NAT problem with ASA using policy routing</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788199#M173324</link>
      <description>&lt;P&gt;I added a second ISP and public IP block to my ASA that is running 9.5.2.&amp;nbsp; I use a route-map and ACL to match internal private IPs that are then sent to the Internet via the second ISP.&amp;nbsp; This seems to work fine for PAT.&lt;/P&gt;
&lt;P&gt;Since it was working well, I decided to use the second ISP for static NAT also.&amp;nbsp; Unfortunately, this is not working so well.&amp;nbsp; I can ping the public IP of static NAT internal hosts but inbound TCP based services like RDP do not work.&amp;nbsp; It doesn't seem to be an ACL issue as the packet trace utility tells me that the packets are allowed and sent to the correct interface.&lt;/P&gt;
&lt;P&gt;On a related note, I cannot ping out or reply to pings on the ASA interface for the second ISP.&amp;nbsp; This happens even thought the IP of that interface has been added to the ACL of the route-map that sends&amp;nbsp;packets out the second ISP.&lt;/P&gt;
&lt;P&gt;So it seems like certain operations, like ping sourced from ASA interface and static NAT are not being correctly policy routed.&amp;nbsp; Below is some relevant config snips.&lt;/P&gt;
&lt;P&gt;Any ideas?&lt;/P&gt;
&lt;P&gt;Thanks,&lt;BR /&gt;Diego&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;ASA Version 9.5(2)&lt;/P&gt;
&lt;P&gt;interface GigabitEthernet0/0&lt;BR /&gt;&amp;nbsp;speed 100&lt;BR /&gt;&amp;nbsp;duplex full&lt;BR /&gt;&amp;nbsp;nameif inf_ISPA&lt;BR /&gt;&amp;nbsp;security-level 0&lt;BR /&gt;&amp;nbsp;ip address 1.1.1.2 255.255.255.224&lt;/P&gt;
&lt;P&gt;interface GigabitEthernet0/1&lt;BR /&gt;&amp;nbsp;speed 1000&lt;BR /&gt;&amp;nbsp;duplex full&lt;BR /&gt;&amp;nbsp;nameif inf_Inside&lt;BR /&gt;&amp;nbsp;security-level 100&lt;BR /&gt;&amp;nbsp;ip address 192.168.1.254 255.255.255.0&lt;BR /&gt;&amp;nbsp;policy-route route-map ALT-GATEWAY&lt;/P&gt;
&lt;P&gt;interface GigabitEthernet0/2&lt;BR /&gt;&amp;nbsp;speed 1000&lt;BR /&gt;&amp;nbsp;duplex full&lt;BR /&gt;&amp;nbsp;nameif inf_ISPB&lt;BR /&gt;&amp;nbsp;security-level 0&lt;BR /&gt;&amp;nbsp;ip address 2.2.2.209 255.255.255.248&lt;/P&gt;
&lt;P&gt;same-security-traffic permit inter-interface&lt;BR /&gt;same-security-traffic permit intra-interface&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;object network SRV1&lt;BR /&gt;&amp;nbsp;host 192.168.1.9&lt;BR /&gt;object network SRV1_ISPB&lt;BR /&gt;&amp;nbsp;host 2.2.2.212&lt;BR /&gt;object network host1_ISPA&lt;BR /&gt;&amp;nbsp;host 192.168.1.15&lt;BR /&gt;object network host2_ISPA&lt;BR /&gt;&amp;nbsp;host 192.168.1.16&lt;/P&gt;
&lt;P&gt;object network net_1&lt;BR /&gt;&amp;nbsp;subnet 192.168.10.0 255.255.255.0&lt;BR /&gt;object network net_2&lt;BR /&gt;&amp;nbsp;subnet 192.168.11.0 255.255.255.0&lt;/P&gt;
&lt;P&gt;object-group network grp_remote_networks&lt;BR /&gt;&amp;nbsp;network-object object net_1&lt;BR /&gt;&amp;nbsp;network-object object net_2&lt;/P&gt;
&lt;P&gt;object-group network grp_NoCXScan&lt;BR /&gt;&amp;nbsp;network-object object CX_Module&lt;BR /&gt;&amp;nbsp;network-object object rtr-1&lt;BR /&gt;&amp;nbsp;network-object object rtr-2&lt;/P&gt;
&lt;P&gt;object-group network PAT_Networks&lt;BR /&gt;&amp;nbsp;network-object object net_data&lt;BR /&gt;&amp;nbsp;network-object object net_voice&lt;BR /&gt;&amp;nbsp;network-object object net_wireless&lt;/P&gt;
&lt;P&gt;access-list inf_ISPB_access_in extended permit icmp any4 any4&lt;BR /&gt;access-list inf_ISPB_access_in extended permit object RDP any object SRV1&lt;/P&gt;
&lt;P&gt;access-list acl_ISPB_Gateway extended deny ip object host1_ISPA any&lt;BR /&gt;access-list acl_ISPB_Gateway extended deny ip object&amp;nbsp;host2_ISPA any&lt;BR /&gt;access-list acl_ISPB_Gateway extended permit ip object inf_ISPB any&lt;BR /&gt;access-list acl_ISPB_Gateway extended permit ip object SRV1 any&lt;BR /&gt;access-list acl_ISPB_Gateway extended permit ip any any&lt;/P&gt;
&lt;P&gt;icmp permit any inf_ISPA&lt;BR /&gt;icmp permit any inf_Inside&lt;BR /&gt;icmp permit any inf_ISPB&lt;/P&gt;
&lt;P&gt;arp timeout 14400&lt;BR /&gt;no arp permit-nonconnected&lt;/P&gt;
&lt;P&gt;nat (inf_Inside,inf_ISPA) source static PAT_Networks PAT_Networks destination static grp_remote_networks grp_remote_networks no-proxy-arp&lt;BR /&gt;!&lt;BR /&gt;object network SRV1&lt;BR /&gt;&amp;nbsp;nat (inf_Inside,inf_ISPB) static SRV1_ISPB&lt;/P&gt;
&lt;P&gt;!&lt;BR /&gt;nat (inf_Inside,inf_ISPA) after-auto source dynamic PAT_Networks interface&lt;BR /&gt;nat (inf_Inside,inf_ISPB) after-auto source dynamic PAT_Networks interface&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;access-group inf_ISPB_access_in in interface inf_ISPB&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;!&lt;BR /&gt;route-map ALT-GATEWAY permit 10&lt;BR /&gt;&amp;nbsp;match ip address acl_ISPB_Gateway&lt;BR /&gt;&amp;nbsp;set ip default next-hop 2.2.2.214&lt;/P&gt;
&lt;P&gt;!&lt;BR /&gt;route inf_ISPA 0.0.0.0 0.0.0.0 1.1.1.1 1&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;sysopt noproxyarp inf_Inside&lt;/P&gt;
&lt;P&gt;!&lt;BR /&gt;class-map CX_Traffic&lt;BR /&gt;&amp;nbsp;match access-list acl_CXTraffic&lt;BR /&gt;class-map tcp_bypass&lt;BR /&gt;&amp;nbsp;description TCP traffic that bypasses stateful firewall&lt;BR /&gt;&amp;nbsp;match access-list acl_TCPbypass&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;policy-map type inspect dns preset_dns_map&lt;BR /&gt;&amp;nbsp;parameters&lt;BR /&gt;&amp;nbsp; message-length maximum client auto&lt;BR /&gt;&amp;nbsp; message-length maximum 512&lt;BR /&gt;policy-map policy1&lt;BR /&gt;&amp;nbsp;class tcp_bypass&lt;BR /&gt;&amp;nbsp; set connection random-sequence-number disable&lt;BR /&gt;&amp;nbsp; set connection advanced-options tcp-state-bypass&lt;BR /&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp;description ASA CX Policy&lt;BR /&gt;&amp;nbsp;class CX_Traffic&lt;BR /&gt;&amp;nbsp; cxsc fail-open&lt;BR /&gt;&amp;nbsp; set connection random-sequence-number disable&lt;BR /&gt;&amp;nbsp;class class-default&lt;BR /&gt;&amp;nbsp; user-statistics accounting&lt;BR /&gt;&amp;nbsp; set connection random-sequence-number disable&lt;BR /&gt;!&lt;BR /&gt;service-policy global_policy global&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:08:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788199#M173324</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2019-03-12T07:08:43Z</dc:date>
    </item>
    <item>
      <title>have you done any packet</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788200#M173325</link>
      <description>&lt;P&gt;have you done any packet tracers? if not run some and post them up if you can.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 21:18:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788200#M173325</guid>
      <dc:creator>Chris Izatt</dc:creator>
      <dc:date>2016-01-26T21:18:47Z</dc:date>
    </item>
    <item>
      <title>Hello Chris,</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788201#M173326</link>
      <description>&lt;P&gt;Hello Chris,&lt;/P&gt;
&lt;P&gt;I opened a TAC case and we confirmed that configuration is correct so we started looking at the possibility of a bug with PBR feature.&amp;nbsp; We did find a bug logged that matches my problem but at the same time we realized we could get it working on the TAC agent's lab environment and also on a different system that I have access to.&amp;nbsp; Going further, I tested on a fourth system and was able to reproduce the bug/problem.&lt;/P&gt;
&lt;P&gt;The interesting thing is that the two systems that have the bug/problem use the same model Comcast modem&amp;nbsp;for the PBR next-hop target.&amp;nbsp; The two systems that work are a lab system and a&amp;nbsp;live system that uses a Cisco router as the PBR next-hop target.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So my gut feeling now tells me that there is something odd about the way the Comcast modem is handling the ASA packets that causes this bug/problem.&amp;nbsp; It would be interesting to find out if the previous guys who logged the bug/problem were also using Comcast or similar cable modem devices but I don't know if that is possible.&lt;/P&gt;
&lt;P&gt;In any case I am going to work with the TAC a bit more and see what we find.&amp;nbsp; I will update the post when we are done.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2016 05:53:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788201#M173326</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2016-01-27T05:53:59Z</dc:date>
    </item>
    <item>
      <title>I love code bugs.   Good Luck</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788202#M173328</link>
      <description>&lt;P&gt;I love code bugs. &amp;nbsp; Good Luck.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2016 16:28:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-problem-with-asa-using-policy-routing/m-p/2788202#M173328</guid>
      <dc:creator>Chris Izatt</dc:creator>
      <dc:date>2016-01-27T16:28:24Z</dc:date>
    </item>
  </channel>
</rss>

