Re: router stress testing tools

From: Dustin Furrer (dustin_at_gorea.com)
Date: 02/07/05

  • Next message: Ghaith Nasrawi: "Re: router stress testing tools" 
    To: "bill williams" <infosecgroup@gmail.com>, <pen-test@securityfocus.com>
Date: Mon, 7 Feb 2005 08:11:37 -0800

    Well, I would think you should use the scanner in question as it may be
    sending a malformed packet or some other sequence of data thats shutting
    down the router, from there you could narrow it down to see what exactly is
    causing it if its not just exhausting the router. But to answer your
    question here are some basic Stress testing utilities that alot of people
    use. Take your pic, it all comes down to preference.

    - Windows -
    UDPFlood
    http://foundstone.com/resources/termsofuse.htm?file=udpflood.zip&warn=true
    Blast
    http://foundstone.com/resources/termsofuse.htm?file=Blast20.zip&warn=true
    FsMax
    http://foundstone.com/resources/termsofuse.htm?file=FSMax20.zip&warn=true
    Solarwinds Wan Killer
    http://www.solarwinds.net/Tools/Miscellaneous/WAN%20Killer/
    Hgod http://packetstormsecurity.nl/DoS/HGod.exe

    - Nix -
    Scapy http://www.cartel-securite.fr/pbiondi/projects/scapy/
    HPing http://www.hping.org/
    Nmap http://www.insecure.org/nmap/
    Gspoof http://gspoof.sourceforge.net/
    Angst http://angst.sourceforge.net/
    Packeth http://packeth.sourceforge.net/

    ----- Original Message -----
    From: "bill williams" <infosecgroup@gmail.com>
    To: <pen-test@securityfocus.com>
    Sent: Saturday, February 05, 2005 2:01 PM
    Subject: router stress testing tools

    > I am looking for information and tools to stress test routers. Any
    > information, white papers, tools, settings for hping, etc. would be
    > appreciated. The incident I am trying to reproduce is related to
    > scanning through the router and the router running out of sessions
    > creating a DOS attack, I think? This testing is in response to yet
    > another "your scanner brought the router, down incident" and I am sure
    > you can imagine the rest. We do have a duplicate router in our testing
    > facility so don't worry I am not trying to DOS anyone.
    >
    > Thank you for your consideration of this request.
    >
    > Disclaimer: I know I have the ability to do my own research and
    > testing, but if you all are nice, it sure could save me a lot of time.
    > Enough time is something most security guys are lacking. This isn't
    > my area of expertise, but I will answer questions on any topics that I
    > know something about. Please send an useless flames to
    > nobody[nospam]@nowhere.com
    >

  • Next message: Ghaith Nasrawi: "Re: router stress testing tools"

    Relevant Pages

    • RE: recover from possible DOS attack!
      ... recover from possible DOS attack! ... If it is a Cisco router you can check and see what's going on ... A good ip to ping is your ISP's end of your Internet connection. ...
      (Security-Basics)
    • Re: recover from possible DOS attack!
      ... recover from possible DOS attack! ... > right there on the router. ... > A good ip to ping is your ISP's end of your Internet connection. ...
      (Security-Basics)
    • Re: recover from possible DOS attack!
      ... recover from possible DOS attack! ... > and RedHat) all connected via a router. ... > router connection (internet connection) and all will be well, ...
      (Security-Basics)
    • Re: Simon is impersonating me.
      ... generated is being construed as a DoS attack. ... The thousands of messages you speak of aren't enough to flood a ...
      (borland.public.delphi.non-technical)
    • Re: Outpost attack from 192.168.1.47!?
      ... So how can a machine that has a private LAN ... >side IP behind the router have a DOS attack from a machine on the Internet ...
      (comp.security.firewalls)