Re: 2.4 and 2.6 under DDoS behavior

From: Trent Lloyd (lathiat_at_bur.st)
Date: 10/16/04

  • Next message: Erwin Schoenmakers: "PROBLEM: while building kernel 2.6.8.1. for Alpha (Miata)"
    Date:	Sat, 16 Oct 2004 22:32:34 +0800
    To: S Iremonger <exxsi@bath.ac.uk>
    
    

    Problem is the linux box in front has to handle double the packets and
    would have to be really fast (e.g. expensive) as well

    > >On Fri, 15 Oct 2004 13:04:22 +0100 (BST), S Iremonger <exxsi@bath.ac.uk> wrote:
    > >> >the external interface was
    > >> >seeing about 600,000 pps at ~350Mbit/sec. The link is 1Gb, so it
    > >> You may want some kind of simpler non-contracking machine infront,
    > >> that has a simpler stateless firewall configuration on it... --
    > >> Maybe 'syncookies firewall' on that machine too....
    >
    > >Possibly, yeah. I guess it depends on if it can keep up with the traffic.
    >
    >
    >
    > I suggest trying out following configuration:-
    >
    > --box infront of the ''firewall'' with:-
    > Optimized kernel WITHOUT connection tracking on nice network
    > devices/drivers...
    > Make SURE the kernel is configured as "optimize as router not host".
    > And -- instigate a **SIMPLE** ruleset (if any rules at all), e.g.
    > just IP addresses and protocol types or something...
    > Install the 'syncookies firewall' on this host, which will answer
    > syn packets from outside with a 'cookie' and expect to see a
    > valid answer to the cookie, and will then (and ONLY THEN) forward
    > connection 'inbounds' to the network...
    >
    > Then have your 'real firewall' with connection tracking, and more
    > complicated ruleset inside that....
    >
    > I'd like to hear anybody's opinions on the above.
    > Maybe what I said is counterproductive, maybe it isn't....
    > I want to hear, in any case.
    >
    > What I *am* preety sure about, is 'connection tracking' (needed for
    > proper NAT as opposed to static 1-1 NAT) DOES slow down your
    > packet passing rate CONSIDERABLY.
    >
    > >Right. It's an Intel 7502 board, dual on board Gig, and a a couple of
    > >Gig cards in the PCI-X slots. All are the newer kind with interrupt
    > >coalescing, but that doesn't matter much with 2.6 and NAPI. One
    > I'm sorry, I dont know that board...
    >
    > >It was a Syn flood, so the easy answer here is to let it through and
    > >let the target hosts deal with it directly.
    > Well, MAYBE, but then MAYBE the SYN flood will just tie up all the
    > conntrack tables ?
    >
    > >I'm not seeking an easy answer, but am wondering what kind of pps
    > >limit people think is reasonable to expect.
    > >Should 1.5M pps be possible, has someone done it?
    > I don't know. sorry.....
    >
    >
    > Good luck, let me know what happens...
    >
    > --S Iremonger <exxsi@bath.ac.uk>
    > -
    > To unsubscribe from this list: send the line "unsubscribe linux-net" in
    > the body of a message to majordomo@vger.kernel.org
    > More majordomo info at http://vger.kernel.org/majordomo-info.html

    -- 
    Trent Lloyd <lathiat@bur.st>
    Bur.st Networking Inc.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Erwin Schoenmakers: "PROBLEM: while building kernel 2.6.8.1. for Alpha (Miata)"

    Relevant Pages

    • Re: possible DoS attack
      ... >> iptables ruleset. ... > what would be a good way to log the packets, ... >>I cannot say if they are really a SYN flood. ... >>> and is there any way i can set ulog in my firewall script to log date ...
      (comp.os.linux.security)
    • Re: possible DoS attack
      ... > iptables ruleset. ... Without seing the ruleset ... what would be a good way to log the packets, ... >I cannot say if they are really a SYN flood. ...
      (comp.os.linux.security)
    • Re: sent an invalid ICMP type 11, code 0 error to a broadcast: 0.0.0.0 on lo?
      ... > packets, ... route add -net 127.0.0.0 netmask 255.0.0.0 dev lo ... There should be no LAN routes going through lo. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: PROBLEM: Oops, nfsd, networking
      ... somewhere between the NFS client and the NFS server, ... when this problem occurs so we can see if there are any bad packets ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: BUG: Slowdown on 3000 socket-machines tracked down
      ... > bug reports are more or less useless and mostly consists of rants): ... > The packets are allocated with GFP_ATOMIC and a lot of traffic ... > overwhelms the free memory. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)