<?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 Re: Policy NAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646440#M592337</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you again for your advice...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will probably give that nat a try either Thursday or Friday...I'll post here when I've made the change...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now one additional thing about the natting...looking at it, it seems it should have no baring on any other natting that is being performed specific to any of the interfaces that we discussed, that is correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Feb 2011 12:00:57 GMT</pubDate>
    <dc:creator>Bruce Summers</dc:creator>
    <dc:date>2011-02-09T12:00:57Z</dc:date>
    <item>
      <title>Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646415#M592296</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I need a little assistance here...I'm trying to do multiple nats...The intent is to nat traffic inbound to isolated/non-routable vlans to the vlan interface to give the appearance the traffic is within the same subnet to keep a couple hundred servers from having to have static routes placed on them....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I presently do this with traffic from vlan 701 and 702 to vlan 760 and 770...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I have a further requirement to nat a single address coming out of vlan 760 to the vlan interface for vlan 770.&amp;nbsp; but, i have not been able to get this to function...and i'm not entirely sure that i can get it to work...below is the configs/info i'm working with...I removed the configs i have tried to use...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Goal:&amp;nbsp; nat a single address, to the inteface of vlan 770 interface ONLY when traffic is destined for vlan 770 without breaking any of the other natting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (Out_of_Band_Server_Mgmt) 1 access-list inside&lt;BR /&gt;nat (EBM_SVCS_2) 1 access-list PNAT702&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;global (Enterprise_Backup_and_Mgmt) 1 interface&lt;BR /&gt;global (Enterprise_Backup_and_Mgmt_2) 1 interface&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;access-list PNAT702 extended permit ip 10.76.169.0 255.255.255.0 192.168.213.0 255.255.255.0&lt;BR /&gt;access-list PNAT702 extended permit icmp 10.76.169.0 255.255.255.0 192.168.213.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside extended permit icmp any any&lt;BR /&gt;access-list inside extended permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Vlan701&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.76.168.1&lt;BR /&gt; nameif Out_of_Band_Server_Mgmt&lt;/P&gt;&lt;P&gt;interface Vlan702&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.76.169.1&lt;BR /&gt; nameif EBM_SVCS_2&lt;/P&gt;&lt;P&gt;interface Vlan760&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.212.1&lt;BR /&gt; nameif Enterprise_Backup_and_Mgmt&lt;/P&gt;&lt;P&gt;interface Vlan770&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.213.1&lt;BR /&gt; nameif Enterprise_Backup_and_Mgmt_2&lt;BR /&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:46:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646415#M592296</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2019-03-11T19:46:43Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646416#M592297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Security level will be the important information that is required to further see how NATing can be done.&lt;/P&gt;&lt;P&gt;Also, can you please share all the current NAT, Global and Static NAT statements with all the corresponding access-list so we can see if there is any overlapping.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 11:55:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646416#M592297</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-08T11:55:13Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646417#M592298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bruce,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;However, I have a further requirement to nat a single address coming out of vlan 760 to the vlan interface for vlan 770.&amp;nbsp; &lt;BR /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Goal:&amp;nbsp; nat a single address, to the inteface of vlan 770 interface ONLY when traffic is destined for vlan 770 without breaking any of the other natting.&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;Are you saying that you want to NAT traffic going from Vlan 760 destined to one of the ip addresses in vlan 770, and the translated ip address should be Vlan 770's interface ip address?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please elaborate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Praveev&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 12:01:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646417#M592298</guid>
      <dc:creator>Praveena Shanubhogue</dc:creator>
      <dc:date>2011-02-08T12:01:33Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646418#M592299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;Thanks Jennifer, &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;All nat and acl info is in my post...there's no other in relation to this natting&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;interface Vlan701&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;&lt;SPAN style="mso-spacerun: yes;"&gt; &lt;/SPAN&gt;security-level 25&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;!&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;interface Vlan702&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;&lt;SPAN style="mso-spacerun: yes;"&gt; &lt;/SPAN&gt;security-level 26&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;!&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;interface Vlan760&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;&lt;SPAN style="mso-spacerun: yes;"&gt; &lt;/SPAN&gt;security-level 20&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;!&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;interface Vlan770&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;&lt;SPAN style="mso-spacerun: yes;"&gt; &lt;/SPAN&gt;security-level 21&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;Bruce&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 12:10:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646418#M592299</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-08T12:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646419#M592300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the response Praveev,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;almost.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to nat a single address in vlan 760 to the interface of vlan 770 when traffic is sourced from 760 destined for 770...the intent is to make the 760 traffic appear as though it is in 770's subnet to keep from having to put static routes on the servers (100's of them)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bruce&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 12:13:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646419#M592300</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-08T12:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646420#M592301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, so traffic is sourced from low security level (20) to high security level (21). You can't just configure dynamic NAT for that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the configuration that you will need:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;static (Enterprise_Backup_and_Mgmt_2,Enterprise_Backup_and_Mgmt) 192.168.213.0 192.168.213.0 netmask 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list Enterprise_Backup_and_Mgmt-NAT permit ip 192.168.212.0 255.255.255.0 192.168.213.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (Enterprise_Backup_and_Mgmt) 1 access-list Enterprise_Backup_and_Mgmt-NAT outside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then "clear xlate" after the above.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 12:54:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646420#M592301</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-08T12:54:34Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646421#M592302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How did it go? Does it work?&lt;/P&gt;&lt;P&gt;If it does, please kindly mark the post as answered and rate useful posts. Otherwise, pls provide more information on the failure and we can assist further.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 22:57:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646421#M592302</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-08T22:57:37Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646422#M592303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm afraid I didn't get a chance to implement/test today...to many fires..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a question, are u a tac engineer? I recognize ur name for some reason.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 23:07:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646422#M592303</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-08T23:07:56Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646423#M592304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good memory, I used to be in the TAC &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 23:13:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646423#M592304</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-08T23:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646424#M592306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Lol...you have helped me many time.  Not with tac any more?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I get this implemented, ill holler and let ya know..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 23:18:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646424#M592306</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-08T23:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646425#M592310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can I pose a separate question concerning running a dhcp service on ur firewall&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 00:16:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646425#M592310</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-09T00:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646426#M592313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure, go ahead.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 00:18:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646426#M592313</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-09T00:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646427#M592315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is running dhcp services for clients very resource intensive? We had a big discussion about whether we should or shouldn't.  But in the end it boils down to is there any "technical" reason we shouldn't.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think no, unless it overly tasks the firewall to do so.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 00:24:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646427#M592315</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-09T00:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646428#M592318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are right, running DHCP services wouldn't be resource intensive. How big is the user base and which model of ASA are you running?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 00:44:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646428#M592318</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-09T00:44:51Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646429#M592321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's actually a FWSM...In this case, we're issuing out, in 3 subnets,&lt;/P&gt;&lt;P&gt;about 150 addresses...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bruce&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 00:48:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646429#M592321</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-09T00:48:56Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646430#M592323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I wouldn't think there will be any problem with running DHCP server on FWSM especially just with 150 addresses.&lt;/P&gt;&lt;P&gt;I saw more problem with DHCP relay feature on FWSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is more information on DHCP server on FWSM for your reference:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/fwsm/fwsm32/configuration/guide/ip_f.html#wp1041659"&gt;http://www.cisco.com/en/US/docs/security/fwsm/fwsm32/configuration/guide/ip_f.html#wp1041659&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 01:02:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646430#M592323</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-09T01:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646431#M592326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good deal...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll use the argument that "cisco tac" says go for it...lol...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 01:05:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646431#M592326</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-09T01:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646432#M592327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ooops &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Ex TAC you mean &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 01:07:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646432#M592327</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-09T01:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646433#M592329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I knew what I meant  &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They wont know...lol...&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Thanks again, and when I blow that config onto that firewall, I'll post&lt;/P&gt;&lt;P&gt;the results and award some points...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 01:09:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646433#M592329</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-09T01:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646434#M592331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;alright&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one more question, if you don't mind...just advise more than anything...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 01:12:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/policy-nat/m-p/1646434#M592331</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2011-02-09T01:12:56Z</dc:date>
    </item>
  </channel>
</rss>

