<?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: PIX &amp; DoS in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-dos/m-p/698758#M1035339</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, how bout if i filter rfc1918, 2827, i'm digging cisco's website and found this url&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801afc76.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801afc76.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this also can be done with PIX, another thing is, is it possible to stop arp attack with pix 6.3(5) , as fas as i know this function only available with pix v7.0 +&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Nov 2006 00:52:53 GMT</pubDate>
    <dc:creator>tonny_ecmyy</dc:creator>
    <dc:date>2006-11-23T00:52:53Z</dc:date>
    <item>
      <title>PIX &amp; DoS</title>
      <link>https://community.cisco.com/t5/network-security/pix-dos/m-p/698755#M1035332</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Currently i'm having trouble with this type of thing, my customer complaint that the PIX doesn't stop the threat, they have set emb_limit, max_conn, ip verify. And also when show ip audit count, large icmp is very high, is this a good news because pix can deny it, or bad news because it can't stop the attack. Any suggestion what is the good config to stop this, they using pix506e 6.3(5) , thank you very much &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 08:59:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dos/m-p/698755#M1035332</guid>
      <dc:creator>tonny_ecmyy</dc:creator>
      <dc:date>2019-03-11T08:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: PIX &amp; DoS</title>
      <link>https://community.cisco.com/t5/network-security/pix-dos/m-p/698756#M1035333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Its not possible to stop traffic arriving to PIX. This must be done on device(s)  in fronf of pix&lt;/P&gt;&lt;P&gt;..PIX can only deny this traffic (stop passing to inside)&lt;/P&gt;&lt;P&gt;We had similar issue and we asked ISP to block this unwanted traffic.. Provider could also implement some ICMP rate-limiting solution or some IPS solution&lt;/P&gt;&lt;P&gt;M.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Nov 2006 09:46:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dos/m-p/698756#M1035333</guid>
      <dc:creator>m.sir</dc:creator>
      <dc:date>2006-11-22T09:46:36Z</dc:date>
    </item>
    <item>
      <title>Re: PIX &amp; DoS</title>
      <link>https://community.cisco.com/t5/network-security/pix-dos/m-p/698757#M1035335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the amount of garbage directed/filtered by PIX is huge, and while waiting for the ISP to respond, create (or add) an ACL denying all ICMP but permit tcp/udp, and apply it on the router Fastethernet interface facing your PIX's outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternate option is to create rate-limit and apply it on serial interface facing internet/ISP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following config example is quiet similar to your scenario:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a008019c6e7.html" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a008019c6e7.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will stop the attack while getting ISP to make their move (sometimes too slow...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Nov 2006 10:52:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dos/m-p/698757#M1035335</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-11-22T10:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: PIX &amp; DoS</title>
      <link>https://community.cisco.com/t5/network-security/pix-dos/m-p/698758#M1035339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, how bout if i filter rfc1918, 2827, i'm digging cisco's website and found this url&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801afc76.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801afc76.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this also can be done with PIX, another thing is, is it possible to stop arp attack with pix 6.3(5) , as fas as i know this function only available with pix v7.0 +&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Nov 2006 00:52:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dos/m-p/698758#M1035339</guid>
      <dc:creator>tonny_ecmyy</dc:creator>
      <dc:date>2006-11-23T00:52:53Z</dc:date>
    </item>
    <item>
      <title>Re: PIX &amp; DoS</title>
      <link>https://community.cisco.com/t5/network-security/pix-dos/m-p/698759#M1035343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RFC 1918 is for you to deny private IP Address (192.168.x.x, 172.16.x.x, 10.x.x.x) on from hitting you back (coming from) from outside, i,e router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RFC2827 is for you to deny your own Public IP range from coming into your network from ISP. It should only go out from your network to ISP. Other unknown Public IP from your network towards ISP also block. But they're allowed to come in from ISP to your network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*ISP to do the same from their end&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can apply RFC 1918 on PIX, while RFC2827 on router (serial intf facing ISP/WAN).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In 6.3(5), ARP attack looks difficult to deny.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In log, you probably will see:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX-4-405001: Received ARP {request | response} collision from &lt;/P&gt;&lt;P&gt;IP_address/mac_address on interface interface_name&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your PIX meet PIX7.0 (or latest) requirements (and $$), maybe you should upgrade it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Nov 2006 01:05:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dos/m-p/698759#M1035343</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-11-23T01:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: PIX &amp; DoS</title>
      <link>https://community.cisco.com/t5/network-security/pix-dos/m-p/698760#M1035347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Man.. why a lot of collisions &amp;amp; deferred on pix outside interface, is this normal?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pix# sh int&lt;/P&gt;&lt;P&gt;interface ethernet0 "outside" is up, line protocol is up&lt;/P&gt;&lt;P&gt; Hardware is i82559 ethernet, address is xxxx.xxxx.xxxx&lt;/P&gt;&lt;P&gt; IP address x.x.x.150, subnet mask 255.255.255.240&lt;/P&gt;&lt;P&gt; MTU 1500 bytes, BW 10000 Kbit half duplex&lt;/P&gt;&lt;P&gt;       49806084 packets input, 1900966895 bytes, 0 no buffer&lt;/P&gt;&lt;P&gt;       Received 28525 broadcasts, 0 runts, 0 giants&lt;/P&gt;&lt;P&gt;       0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort&lt;/P&gt;&lt;P&gt;       74851548 packets output, 665950688 bytes, 0 underruns&lt;/P&gt;&lt;P&gt;       0 output errors, 1566555 collisions, 0 interface resets&lt;/P&gt;&lt;P&gt;       0 babbles, 0 late collisions, 412197 deferred&lt;/P&gt;&lt;P&gt;       0 lost carrier, 0 no carrier&lt;/P&gt;&lt;P&gt;       input queue (curr/max blocks): hardware (128/128) software (0/23)&lt;/P&gt;&lt;P&gt;       output queue (curr/max blocks): hardware (0/128) software (0/1)&lt;/P&gt;&lt;P&gt;interface ethernet1 "inside" is up, line protocol is up&lt;/P&gt;&lt;P&gt; Hardware is i82559 ethernet, address is xxxx.xxxx.xxxx&lt;/P&gt;&lt;P&gt; IP address 192.168.x.x, subnet mask 255.255.255.0&lt;/P&gt;&lt;P&gt; MTU 1500 bytes, BW 100000 Kbit full duplex&lt;/P&gt;&lt;P&gt;       74215126 packets input, 638648644 bytes, 0 no buffer&lt;/P&gt;&lt;P&gt;       Received 135138 broadcasts, 0 runts, 0 giants&lt;/P&gt;&lt;P&gt;       0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort&lt;/P&gt;&lt;P&gt;       48419528 packets output, 1787016600 bytes, 0 underruns&lt;/P&gt;&lt;P&gt;       0 output errors, 0 collisions, 0 interface resets&lt;/P&gt;&lt;P&gt;       0 babbles, 0 late collisions, 0 deferred&lt;/P&gt;&lt;P&gt;       0 lost carrier, 0 no carrier&lt;/P&gt;&lt;P&gt;       input queue (curr/max blocks): hardware (128/128) software (0/28)&lt;/P&gt;&lt;P&gt;       output queue (curr/max blocks): hardware (2/66) software (0/1)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Nov 2006 02:04:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dos/m-p/698760#M1035347</guid>
      <dc:creator>tonny_ecmyy</dc:creator>
      <dc:date>2006-11-23T02:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: PIX &amp; DoS</title>
      <link>https://community.cisco.com/t5/network-security/pix-dos/m-p/698761#M1035350</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ohhh man... i find this&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.securiteam.com/securitynews/5AP032AI0A.html" target="_blank"&gt;http://www.securiteam.com/securitynews/5AP032AI0A.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and its related to this&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_security_notice09186a0080624a37.html" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_security_notice09186a0080624a37.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;and how do i download the software 6.3(5.106).  because i dont have the access to that area. Any one.. please give me the software... mail to &lt;A href="mailto:tony.g@wtexcellence.com.my"&gt;tony.g@wtexcellence.com.my&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help, i'm in big trouble, thank you very much&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Nov 2006 02:35:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dos/m-p/698761#M1035350</guid>
      <dc:creator>tonny_ecmyy</dc:creator>
      <dc:date>2006-11-23T02:35:24Z</dc:date>
    </item>
  </channel>
</rss>

