<?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: basic pix problem inbound &amp; outbound traffic.... in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/basic-pix-problem-inbound-outbound-traffic/m-p/490615#M535112</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for time Harish. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the best...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Jul 2005 11:36:33 GMT</pubDate>
    <dc:creator>after1111</dc:creator>
    <dc:date>2005-07-20T11:36:33Z</dc:date>
    <item>
      <title>basic pix problem inbound &amp; outbound traffic....</title>
      <link>https://community.cisco.com/t5/network-security/basic-pix-problem-inbound-outbound-traffic/m-p/490613#M535109</link>
      <description>&lt;P&gt;I have a problem with pinging. I can ping to workstations on the 192.168.100.x network but I cant ping the outbound interface (e0) onthe same network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second problem is I can ping from outside to inside, ive set acl and static route but didnt work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just want to pc1 to be able to get through pix to pc 2 and vice versa. Please give me a sample configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here's the config:&lt;/P&gt;&lt;P&gt;PIX Version 6.3(4)&lt;/P&gt;&lt;P&gt;interface ethernet0 auto&lt;/P&gt;&lt;P&gt;interface ethernet1 auto&lt;/P&gt;&lt;P&gt;interface ethernet2 auto shutdown&lt;/P&gt;&lt;P&gt;nameif ethernet0 outside security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;nameif ethernet2 intf2 security4&lt;/P&gt;&lt;P&gt;enable password xxx&lt;/P&gt;&lt;P&gt;passwd xxx&lt;/P&gt;&lt;P&gt;hostname pixfirewall&lt;/P&gt;&lt;P&gt;fixup protocol dns maximum-length 512&lt;/P&gt;&lt;P&gt;fixup protocol ftp 21&lt;/P&gt;&lt;P&gt;fixup protocol h323 h225 1720&lt;/P&gt;&lt;P&gt;fixup protocol h323 ras 1718-1719&lt;/P&gt;&lt;P&gt;fixup protocol http 80&lt;/P&gt;&lt;P&gt;fixup protocol rsh 514&lt;/P&gt;&lt;P&gt;fixup protocol rtsp 554&lt;/P&gt;&lt;P&gt;fixup protocol sip 5060&lt;/P&gt;&lt;P&gt;fixup protocol sip udp 5060&lt;/P&gt;&lt;P&gt;fixup protocol skinny 2000&lt;/P&gt;&lt;P&gt;fixup protocol smtp 25&lt;/P&gt;&lt;P&gt;fixup protocol sqlnet 1521&lt;/P&gt;&lt;P&gt;fixup protocol tftp 69&lt;/P&gt;&lt;P&gt;names&lt;/P&gt;&lt;P&gt;access-list acl_out permit icmp any any&lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;mtu intf2 1500&lt;/P&gt;&lt;P&gt;ip address outside 192.168.100.1 255.255.255.0&lt;/P&gt;&lt;P&gt;ip address inside 192.168.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt;no ip address intf2&lt;/P&gt;&lt;P&gt;ip audit info action alarm&lt;/P&gt;&lt;P&gt;ip audit attack action alarm&lt;/P&gt;&lt;P&gt;pdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;global (outside) 1 192.168.100.150-192.168.100.200 netmask 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside) 1 0.0.0.0 0.0.0.0 0 0&lt;/P&gt;&lt;P&gt;access-group acl_out in interface outside&lt;/P&gt;&lt;P&gt;timeout xlate 3:00:00&lt;/P&gt;&lt;P&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00&lt;/P&gt;&lt;P&gt;timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00&lt;/P&gt;&lt;P&gt;timeout uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ protocol tacacs+&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ max-failed-attempts 3&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ deadtime 10&lt;/P&gt;&lt;P&gt;aaa-server RADIUS protocol radius&lt;/P&gt;&lt;P&gt;aaa-server RADIUS max-failed-attempts 3&lt;/P&gt;&lt;P&gt;aaa-server RADIUS deadtime 10&lt;/P&gt;&lt;P&gt;aaa-server LOCAL protocol local&lt;/P&gt;&lt;P&gt;no snmp-server location&lt;/P&gt;&lt;P&gt;no snmp-server contact&lt;/P&gt;&lt;P&gt;snmp-server community public&lt;/P&gt;&lt;P&gt;no snmp-server enable traps&lt;/P&gt;&lt;P&gt;floodguard enable&lt;/P&gt;&lt;P&gt;telnet timeout 5&lt;/P&gt;&lt;P&gt;ssh timeout 5&lt;/P&gt;&lt;P&gt;console timeout 0&lt;/P&gt;&lt;P&gt;terminal width 80&lt;/P&gt;&lt;P&gt;Cryptochecksum:xxx&lt;/P&gt;&lt;P&gt;: end&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:16:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/basic-pix-problem-inbound-outbound-traffic/m-p/490613#M535109</guid>
      <dc:creator>after1111</dc:creator>
      <dc:date>2020-02-21T08:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: basic pix problem inbound &amp; outbound traffic....</title>
      <link>https://community.cisco.com/t5/network-security/basic-pix-problem-inbound-outbound-traffic/m-p/490614#M535111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are not able to ping the outside interface of the pix from inside host, but able to ping the outside host from the inside host. it is fine. As it is security feature designed in pix ASA. You can't ping the interface ip address of the pix from the host connected to the other interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the other issue, please try the following command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;static (inside,outside) &lt;PUBLIC_IP&gt; &lt;INSIDE_HOST_IP&gt;&lt;/INSIDE_HOST_IP&gt;&lt;/PUBLIC_IP&gt;&lt;/P&gt;&lt;P&gt;wr mem&lt;/P&gt;&lt;P&gt;cl xlate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where, &lt;PUBLIC_IP&gt; is the free public ip address in the pool that can be used to map the pc1 on the inside.&lt;/PUBLIC_IP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other configuraiton looks fine. If you have any questions, please feel free to contact me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Harish Tandon&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:harishtandon23@gmail.com"&gt;harishtandon23@gmail.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jul 2005 11:31:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/basic-pix-problem-inbound-outbound-traffic/m-p/490614#M535111</guid>
      <dc:creator>harishtandon23</dc:creator>
      <dc:date>2005-07-20T11:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: basic pix problem inbound &amp; outbound traffic....</title>
      <link>https://community.cisco.com/t5/network-security/basic-pix-problem-inbound-outbound-traffic/m-p/490615#M535112</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for time Harish. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the best...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jul 2005 11:36:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/basic-pix-problem-inbound-outbound-traffic/m-p/490615#M535112</guid>
      <dc:creator>after1111</dc:creator>
      <dc:date>2005-07-20T11:36:33Z</dc:date>
    </item>
  </channel>
</rss>

