<?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 command doubt in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-command-doubt/m-p/1448951#M659789</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kureli beat me to it--please disregard &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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi Subodh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the scenario you describe, you will want to configure the first static statement (and the corresponding access rules):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;static (inside,outside) 2.2.2.2 192.168.1.1&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second line you mentioned would only be used if you wanted to do what is called "outside NAT". With that line, users on the inside would see 2.2.2.2 as an internal IP address, 192.168.1.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Aug 2010 12:04:34 GMT</pubDate>
    <dc:creator>mirober2</dc:creator>
    <dc:date>2010-08-10T12:04:34Z</dc:date>
    <item>
      <title>Static command doubt</title>
      <link>https://community.cisco.com/t5/network-security/static-command-doubt/m-p/1448949#M659738</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;If we have following static commends&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 2.2.2.2&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.1.1&amp;nbsp;&amp;nbsp; (&amp;nbsp; Public-routable-ip, private-ip)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (outside,inside)&amp;nbsp; 192.168.1.1 2.2.2.2&amp;nbsp; ( private-ip,public-routable-ip)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and corresponding permit access-list is configured.&amp;nbsp; Will these commands will have the same effect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As there is always one-to-one mapping. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When there is a packet with destination 2.2.2.2 arriving on outside interface&amp;nbsp; then&amp;nbsp; it's destination IP address will be replaced by 192.168.1.1 and&lt;/P&gt;&lt;P&gt;packet will be forwarded to that host from inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In second static&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, if packet source is 192.168.1.1 and&amp;nbsp; destination can be anything then while packet is exiting the outside interface then it's source ip address will&lt;/P&gt;&lt;P&gt;be over written by 2.2.2.2 and then packet is forwarded to outside world.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is this understanding correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate you help.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Subodh&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:23:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-command-doubt/m-p/1448949#M659738</guid>
      <dc:creator>bapatsubodh</dc:creator>
      <dc:date>2019-03-11T18:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: Static command doubt</title>
      <link>https://community.cisco.com/t5/network-security/static-command-doubt/m-p/1448950#M659765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;static (inside,outside) 2.2.2.2&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.1.1&amp;nbsp;&amp;nbsp; (&amp;nbsp; Public-routable-ip, private-ip)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When there is a packet with destination 2.2.2.2 arriving on outside interface&amp;nbsp; then&amp;nbsp; it's destination IP address will be replaced by 192.168.1.1 and&lt;/P&gt;&lt;P&gt;packet will be forwarded to that host from inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, if packet source is 192.168.1.1 and&amp;nbsp; destination can be anything then while packet is exiting the outside interface then it's source ip address will&lt;/P&gt;&lt;P&gt;be over written by 2.2.2.2 and then packet is forwarded to outside world.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding: 0px; min-height: 8pt; height: 8pt;"&gt;###############################################################&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (outside,inside)&amp;nbsp; 192.168.1.1 2.2.2.2&amp;nbsp; ( private-ip,public-routable-ip)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the source of the packet is 2.2.2.2 its source will be changed to 192.168.1.1 when it enters the inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Aug 2010 12:01:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-command-doubt/m-p/1448950#M659765</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-08-10T12:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: Static command doubt</title>
      <link>https://community.cisco.com/t5/network-security/static-command-doubt/m-p/1448951#M659789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kureli beat me to it--please disregard &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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi Subodh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the scenario you describe, you will want to configure the first static statement (and the corresponding access rules):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;static (inside,outside) 2.2.2.2 192.168.1.1&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second line you mentioned would only be used if you wanted to do what is called "outside NAT". With that line, users on the inside would see 2.2.2.2 as an internal IP address, 192.168.1.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Aug 2010 12:04:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-command-doubt/m-p/1448951#M659789</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2010-08-10T12:04:34Z</dc:date>
    </item>
  </channel>
</rss>

