<?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: Static NAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-nat/m-p/728701#M978296</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pal,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Find below the syntax of static command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (real_interface,mapped_interface) {mapped_address | interface} real_address [netmask mask]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here &lt;/P&gt;&lt;P&gt;real_interface = inside &lt;/P&gt;&lt;P&gt;     mapped_interface = outside&lt;/P&gt;&lt;P&gt;     mapped_address = 10.254.254.0&lt;/P&gt;&lt;P&gt;     real_address = 10.7.0.0&lt;/P&gt;&lt;P&gt;     netmask = 255.255.248.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it becomes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 10.254.254.0 10.7.0.0 netmask 255.255.248.0 0 0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Modify your access-list to allow access to 10.254.254.0 as destination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this is Helpdul&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Jun 2007 11:32:00 GMT</pubDate>
    <dc:creator>satish_zanjurne</dc:creator>
    <dc:date>2007-06-18T11:32:00Z</dc:date>
    <item>
      <title>Static NAT</title>
      <link>https://community.cisco.com/t5/network-security/static-nat/m-p/728698#M978293</link>
      <description>&lt;P&gt;When configuring static nat (inside, outside) shouldn't the subnet address usedin the static (inside, outside) command be in the same subnet as the inside or outside interface IP address. One of my customer is saying it doesn't have to be.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:31:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat/m-p/728698#M978293</guid>
      <dc:creator>astanislaus</dc:creator>
      <dc:date>2019-03-11T10:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: Static NAT</title>
      <link>https://community.cisco.com/t5/network-security/static-nat/m-p/728699#M978294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.You use static alongwith access-list for mapping the Hosts which you want to make available to public/partner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.It makes sense using the same subnet address as of Outside interface for mapped/global static address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not seen anybody implementing out of this scope,neither i have read it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2007 07:55:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat/m-p/728699#M978294</guid>
      <dc:creator>satish_zanjurne</dc:creator>
      <dc:date>2007-06-18T07:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: Static NAT</title>
      <link>https://community.cisco.com/t5/network-security/static-nat/m-p/728700#M978295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Problem is attached:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After puting the following command customer is seeing ARP Storm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 10.7.0.0 10.7.0.0 netmask 255.255.248.0 0 0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2007 09:14:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat/m-p/728700#M978295</guid>
      <dc:creator>astanislaus</dc:creator>
      <dc:date>2007-06-18T09:14:55Z</dc:date>
    </item>
    <item>
      <title>Re: Static NAT</title>
      <link>https://community.cisco.com/t5/network-security/static-nat/m-p/728701#M978296</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pal,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Find below the syntax of static command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (real_interface,mapped_interface) {mapped_address | interface} real_address [netmask mask]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here &lt;/P&gt;&lt;P&gt;real_interface = inside &lt;/P&gt;&lt;P&gt;     mapped_interface = outside&lt;/P&gt;&lt;P&gt;     mapped_address = 10.254.254.0&lt;/P&gt;&lt;P&gt;     real_address = 10.7.0.0&lt;/P&gt;&lt;P&gt;     netmask = 255.255.248.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it becomes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 10.254.254.0 10.7.0.0 netmask 255.255.248.0 0 0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Modify your access-list to allow access to 10.254.254.0 as destination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this is Helpdul&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2007 11:32:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat/m-p/728701#M978296</guid>
      <dc:creator>satish_zanjurne</dc:creator>
      <dc:date>2007-06-18T11:32:00Z</dc:date>
    </item>
  </channel>
</rss>

