<?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 Hi, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037576#M144968</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Along with the packet tracer, if possible, please run the below debug&amp;nbsp;&lt;/P&gt;
&lt;P&gt;debug policy-route&lt;/P&gt;
&lt;P&gt;this will give us an idea if the policy is working as expected or not.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Akhil&lt;/P&gt;</description>
    <pubDate>Mon, 17 Apr 2017 14:56:12 GMT</pubDate>
    <dc:creator>Akhil.Balachandran</dc:creator>
    <dc:date>2017-04-17T14:56:12Z</dc:date>
    <item>
      <title>ASA PBR issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037572#M144963</link>
      <description>&lt;P&gt;hi, i facing a PBR issue on ASA,&lt;/P&gt;
&lt;P&gt;as i know , the normal PBR format is:&lt;/P&gt;
&lt;P&gt;access-list to_ADSL extended permit ip 192.168.1.0 255.255.255.0 any&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;route-map my_map permit 100&lt;BR /&gt; match ip address to_ADSL&lt;BR /&gt; set ip next-hop 100.0.0.1&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;then apply it on the interface.&lt;/P&gt;
&lt;P&gt;but now,&amp;nbsp; my ip is dynamic...&lt;/P&gt;
&lt;P&gt;so there is no way to know what is the next hop IP.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;so i tried this :&lt;/P&gt;
&lt;P&gt;access-list to_ADSL extended permit ip 192.168.1.0 255.255.255.0 any&lt;/P&gt;
&lt;P&gt;route-map my_map permit 100&lt;BR /&gt; match ip address to_ADSL&lt;BR /&gt; set interface ADSL_if&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;then apply it on the interface. BUT,&amp;nbsp; not work, how to set a PBR as the ip is dynamic...&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;thx&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 09:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037572#M144963</guid>
      <dc:creator>ronald.su</dc:creator>
      <dc:date>2019-03-12T09:13:48Z</dc:date>
    </item>
    <item>
      <title>my adsl interface IP is</title>
      <link>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037573#M144964</link>
      <description>&lt;P&gt;my adsl interface IP is assign by pppoe and it's dynamic&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2017 07:54:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037573#M144964</guid>
      <dc:creator>ronald.su</dc:creator>
      <dc:date>2017-04-17T07:54:48Z</dc:date>
    </item>
    <item>
      <title>Configuration looks ok .</title>
      <link>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037574#M144965</link>
      <description>&lt;P&gt;Configuration looks ok .&lt;/P&gt;
&lt;P&gt;Can you run packet tracer from ASA ? replace LAN with your configured name. I hope you have taken care of NAT configuration.&lt;/P&gt;
&lt;P&gt;packet-tracer input LAN tcp 192.168.1.1 443 8.8.8.8 443&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Ajay&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2017 07:57:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037574#M144965</guid>
      <dc:creator>ajay chauhan</dc:creator>
      <dc:date>2017-04-17T07:57:35Z</dc:date>
    </item>
    <item>
      <title>i will try packet tracer</title>
      <link>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037575#M144966</link>
      <description>&lt;P&gt;i will try packet tracer after office hours, my nat config is ok, because if i dont define a default route, the ASA will get a default route from pppoe, and the traffice can go out normally. so the nat is ok&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2017 09:09:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037575#M144966</guid>
      <dc:creator>ronald.su</dc:creator>
      <dc:date>2017-04-17T09:09:03Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037576#M144968</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Along with the packet tracer, if possible, please run the below debug&amp;nbsp;&lt;/P&gt;
&lt;P&gt;debug policy-route&lt;/P&gt;
&lt;P&gt;this will give us an idea if the policy is working as expected or not.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Akhil&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2017 14:56:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pbr-issue/m-p/3037576#M144968</guid>
      <dc:creator>Akhil.Balachandran</dc:creator>
      <dc:date>2017-04-17T14:56:12Z</dc:date>
    </item>
  </channel>
</rss>

