<?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: Traceroute thru FWSM in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189076#M860965</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;Any clues.. what could be the issue&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RBK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 11 Apr 2009 07:05:43 GMT</pubDate>
    <dc:creator>hclisschennai</dc:creator>
    <dc:date>2009-04-11T07:05:43Z</dc:date>
    <item>
      <title>Traceroute thru FWSM</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189075#M860957</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am configuring FWSM with INSIDE and OUTSIDE interface (zones). For testing I have configured the access-list as below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list OUTSIDE permit ip any any&lt;/P&gt;&lt;P&gt;access-list OUTSIDE permit icmp any any&lt;/P&gt;&lt;P&gt;access-list INSIDE permit ip any any&lt;/P&gt;&lt;P&gt;access-list INSIDE permit icmp any any&lt;/P&gt;&lt;P&gt;access-group OUTSIDE in interface OUTSIDE&lt;/P&gt;&lt;P&gt;access-group INSIDE in interface INSIDE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have connected SUN SOLARIS servers and Windows Servers in INSIDE interface.I am able to ping the destination IP address from both SUN SOLARIS &amp;amp; WINDOWS SERVER when i give traceroute from SUN SERVERS it is showing entire hops inbetween the Server and destination IP Address. But where as if i give it from Windows Server it is showing * * * * and after 3 Hops is showing only the Destination IP address. I am surprised whether it is the behaviour of Operating systems or FWSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please guide me&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;R.B.Kumar&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:17:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189075#M860957</guid>
      <dc:creator>hclisschennai</dc:creator>
      <dc:date>2019-03-11T15:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute thru FWSM</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189076#M860965</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;Any clues.. what could be the issue&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RBK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Apr 2009 07:05:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189076#M860965</guid>
      <dc:creator>hclisschennai</dc:creator>
      <dc:date>2009-04-11T07:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute thru FWSM</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189077#M860969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Dear,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hve you configured the inspection for the icmp_error and please let me know if this fix your problem.Also don't forget have icmp allow ACL's from source to destination in dual direction. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a set of FWSM running 3.2(1)got similar kind of error. So Talk in CISCO TAC. The bug ID TAC gave me is: CSCsj53485 &lt;/P&gt;&lt;P&gt;From what I was told, this affects version 3.1(5) and 3.1(6) and will be addressed in 3.1(7) &lt;/P&gt;&lt;P&gt;It seems it also affects 3.2(1) and will be addressed in 3.2(2) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be helpful if you can talk to CISCO TAC about this, and if they  inform you of a bug ID. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know what is the current version used and the bug ID if you get from CISCO TAC and also what new version TAC suggested.This would be helpful for us also. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Apr 2009 01:36:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189077#M860969</guid>
      <dc:creator>sachinga.hcl</dc:creator>
      <dc:date>2009-04-13T01:36:21Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute thru FWSM</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189078#M860973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sachin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your comments.I am using the below version of FWSM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FWSM Version 3.1(12) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please share your inputs on this. I am interested to know you also faced similar issue. Please let me know the resolution too&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;R.B.Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Apr 2009 17:27:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-thru-fwsm/m-p/1189078#M860973</guid>
      <dc:creator>hclisschennai</dc:creator>
      <dc:date>2009-04-13T17:27:40Z</dc:date>
    </item>
  </channel>
</rss>

