Ddos syn flood (cpu - ram or network card)

Discussion in 'Site & Server Administration' started by ASTRAPI, Jan 4, 2010.

  1. #1
    Hello

    In a ddos syn flood attack in a fast server:

    # 2x Intel Xeon Quad 5405
    # 8192 MB FB DDR2 RAM
    # 500 GB 7.200 RPM
    # 1.000 Mbit unshared port


    I want to ask if the problem will be the cpu ram or the network card to hold as much traffic is possible for a forum?

    Thank you
     
    ASTRAPI, Jan 4, 2010 IP
  2. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #2
    Depends on what services they are flooding, if it's web pages, what web pages they are flooding.

    If they are hitting pages that are generated dynamically, your first bottleneck will probably be your DB server's inability to do that many SQL queries.

    If they are not hitting dynamically generated pages, your first bottleneck will probably be the number of concurrent requests your web server can fulfill.
     
    digitalpoint, Jan 4, 2010 IP
  3. ASTRAPI

    ASTRAPI Guest

    Messages:
    500
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Thank for you fast responce digitalpoint :)

    What i can do for those two scenarios to protect my server or to be able to handle that?

    Does extra ram helps the performance of my sql in tha scenario?
     
    ASTRAPI, Jan 4, 2010 IP
  4. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #4
    Not really, no... your best bet is to block it before it gets to your server (at the firewall or router level).
     
    digitalpoint, Jan 4, 2010 IP
  5. ASTRAPI

    ASTRAPI Guest

    Messages:
    500
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #5
    ok thanks.
     
    ASTRAPI, Jan 4, 2010 IP