<?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 Firewall needs to access server from same segment but from outsi in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838345#M490704</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Abhinay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please describe this in more brief?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You've two servers in your network 192.168.1.0/24.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And you want to translate both of them to 1.2.3.4? Am i right in understanding this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you want to access this web-server 192.168.1.2 using its translated ip address 1.2.3.4 from the inside network "192.168.1.0/24"?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If yes,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then think about this .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. You initiate a packet from a Client 192.168.1.10 to abc.com.&lt;/P&gt;&lt;P&gt;2. Your Local DNS server resolves it to 1.2.3.4 and provides this ip address to the Client.&lt;/P&gt;&lt;P&gt;3. Now 192.168.1.10 initiates a packet to 1.2.3.4 and sends it to the ASA , as ASA is default gateway of this Client.&lt;/P&gt;&lt;P&gt;4. ASA does routing lookup and has a route for 0.0.0.0 0.0.0.0 pointing on outside, so as per ASA this destination ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; address 1.2.3.4 is on the outside interface. &lt;/P&gt;&lt;P&gt;5. After routing lookup ASA finds that this ip address 1.2.3.4 on outside is translated to 192.168.1.2 on inside and&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; should go back to inside network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. ASA cannot allow this , as this same packet tries to go from inside to outside and again back to inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So we can do hair-pinning in this solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,inside) 1.2.3.4 192.168.1.2 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This gives ASA an xlate on the inside interface and if ASA receives a packet on the inside interface for 1.2.3.4 ip address, ASA u-turns that packet (by default not allowed) back to the inside network and sends it to the 192.168.1.2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check this&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968d1.shtml#solution2"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968d1.shtml#solution2&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you've any further doubts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Puneet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Dec 2011 12:35:34 GMT</pubDate>
    <dc:creator>puseth</dc:creator>
    <dc:date>2011-12-20T12:35:34Z</dc:date>
    <item>
      <title>Firewall needs to access server from same segment but from outside..</title>
      <link>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838343#M490702</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have one segment below to the Firewall i.e LAN-&amp;gt; 192.168.1.0/24 from this segment I have one server 192.168.1.2 is translating to suppose 1.2.3.4/32 and I have one more server that is DNS server with translating with same IP 1.2.3.4. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now my problem is if I want to access the 192.168.1.2 the server from the same segment it should have to be access from outside (suppose traffic initiate from 192.168.1.0/24, request need have to go outside and come back 192.168.1.2 wiht translation or anything no problem)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me on same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Abhinay&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:03:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838343#M490702</guid>
      <dc:creator>abhi-adte</dc:creator>
      <dc:date>2019-03-11T22:03:59Z</dc:date>
    </item>
    <item>
      <title>Firewall needs to access server from same segment but from outsi</title>
      <link>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838344#M490703</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;192.168.1.2 --&amp;gt; web server&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 05:00:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838344#M490703</guid>
      <dc:creator>abhi-adte</dc:creator>
      <dc:date>2011-12-20T05:00:17Z</dc:date>
    </item>
    <item>
      <title>Firewall needs to access server from same segment but from outsi</title>
      <link>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838345#M490704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Abhinay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please describe this in more brief?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You've two servers in your network 192.168.1.0/24.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And you want to translate both of them to 1.2.3.4? Am i right in understanding this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you want to access this web-server 192.168.1.2 using its translated ip address 1.2.3.4 from the inside network "192.168.1.0/24"?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If yes,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then think about this .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. You initiate a packet from a Client 192.168.1.10 to abc.com.&lt;/P&gt;&lt;P&gt;2. Your Local DNS server resolves it to 1.2.3.4 and provides this ip address to the Client.&lt;/P&gt;&lt;P&gt;3. Now 192.168.1.10 initiates a packet to 1.2.3.4 and sends it to the ASA , as ASA is default gateway of this Client.&lt;/P&gt;&lt;P&gt;4. ASA does routing lookup and has a route for 0.0.0.0 0.0.0.0 pointing on outside, so as per ASA this destination ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; address 1.2.3.4 is on the outside interface. &lt;/P&gt;&lt;P&gt;5. After routing lookup ASA finds that this ip address 1.2.3.4 on outside is translated to 192.168.1.2 on inside and&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; should go back to inside network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. ASA cannot allow this , as this same packet tries to go from inside to outside and again back to inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So we can do hair-pinning in this solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,inside) 1.2.3.4 192.168.1.2 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This gives ASA an xlate on the inside interface and if ASA receives a packet on the inside interface for 1.2.3.4 ip address, ASA u-turns that packet (by default not allowed) back to the inside network and sends it to the 192.168.1.2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check this&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968d1.shtml#solution2"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968d1.shtml#solution2&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you've any further doubts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Puneet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 12:35:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838345#M490704</guid>
      <dc:creator>puseth</dc:creator>
      <dc:date>2011-12-20T12:35:34Z</dc:date>
    </item>
    <item>
      <title>Firewall needs to access server from same segment but from outsi</title>
      <link>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838346#M490705</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Excellent thank a lot... its works... &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Dec 2011 10:16:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838346#M490705</guid>
      <dc:creator>abhi-adte</dc:creator>
      <dc:date>2011-12-26T10:16:26Z</dc:date>
    </item>
    <item>
      <title>Firewall needs to access server from same segment but from outsi</title>
      <link>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838347#M490706</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also when I was trying to do some research in same thing that is Land attack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Static (in,in) also can mitigate this issue that's my observation if need corrections please let me know.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Dec 2011 10:26:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-needs-to-access-server-from-same-segment-but-from/m-p/1838347#M490706</guid>
      <dc:creator>abhi-adte</dc:creator>
      <dc:date>2011-12-26T10:26:20Z</dc:date>
    </item>
  </channel>
</rss>

