Rate limit ICMP to prevent dDoS

Linux Advanced Routing & Traffic Control HOWTO
Prev | Chapter 15. Cookbook | Next

# 15.3. Rate limit ICMP to prevent dDoS

Recently, distributed denial of service attacks have become a major nuisance on the Internet. By properly filtering and rate limiting your network, you can both prevent becoming a casualty or the cause of these attacks.

You should filter your networks so that you do not allow non-local IP source addressed packets to leave your network. This stops people from anonymously sending junk to the Internet.

Rate limiting goes much as shown earlier. To refresh your memory, our ASCIIgram again:

    [The Internet] ---<E3, T3, whatever>--- [Linux router] --- [Office+ISP]
                                          eth1          eth0

We first set up the prerequisite parts:

    # tc qdisc add dev eth0 root handle 10: cbq bandwidth 10Mbit avpkt 1000
    # tc class add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 10Mbit rate \
      10Mbit allot 1514 prio 5 maxburst 20 avpkt 1000

If you have 100Mbit, or more, interfaces, adjust these numbers. Now you need to determine how much ICMP traffic you want to allow. You can perform measurements with tcpdump, by having it write to a file for a while, and seeing how much ICMP passes your network. Do not forget to raise the snapshot length!

If measurement is impractical, you might want to choose 5% of your available bandwidth. Let's set up our class:

    # tc class add dev eth0 parent 10:1 classid 10:100 cbq bandwidth 10Mbit rate \
      100Kbit allot 1514 weight 800Kbit prio 5 maxburst 20 avpkt 250 \
      bounded

This limits at 100Kbit. Now we need a filter to assign ICMP traffic to this class:

    # tc filter add dev eth0 parent 10:0 protocol ip prio 100 u32 match ip
      protocol 1 0xFF flowid 10:100

Prev | Home | Next
Protecting your host from SYN floods | Up | Prioritizing interactive traffic