Someone might attack on your system. You can drop attacker IP using IPtables. However, you can use route command to null route unwanted traffic. A null route (also called as blackhole route) is a network route or kernel routing table entry that goes nowhere. Matching packets are dropped (ignored) rather than forwarded, acting as a kind of very limited firewall. The act of using null routes is often called blackhole filtering.
You can nullroute (like some time ISP do prevent your network device from sending any data to a remote system.) stopping various attacks coming from a single IP (read as spammers or hackers):
Nullroute IP using route command
Suppose that bad IP is 65.21.34.4, type following command at shell:
# route add 65.21.34.4 gw 127.0.0.1 lo
You can verify it with following command:
# netstat -nr
OR
# route -n
You can also use reject target (thanks to Gabriele):
# route add -host IP-ADDRESS reject
# route add -host 64.1.2.3 reject
To confirm the null routing status, use ip command as follows:
# ip route get 64.1.2.3
Output:
RTNETLINK answers: Network is unreachable
Drop entire subnet 192.67.16.0/24:
# route add -net 192.67.16.0/24 gw 127.0.0.1 lo
You can also use ip command to null route network or ip, enter:
# ip route add blackhole 202.54.5.2/29
# route -n
How do I remove null routing? How do I remove blocked IP address?
Simple use router delete command,
# route delete 65.21.34.4
This is cool, as you do not have to play with iptables rules.
See also:
- man pages route, ip and netstat command
- Blocking incoming access to selected/specific ip address
- How do I block outgoing access to selected/specific ip address?
Updated for accuracy.
Featured Articles:
- 20 Linux System Monitoring Tools Every SysAdmin Should Know
- 20 Linux Server Hardening Security Tips
- Linux: 20 Iptables Examples For New SysAdmins

- My 10 UNIX Command Line Mistakes
- 25 PHP Security Best Practices For Sys Admins
- The Novice Guide To Buying A Linux Laptop
- Top 5 Email Client For Linux, Mac OS X, and Windows Users
- Top 20 OpenSSH Server Best Security Practices
- Top 10 Open Source Web-Based Project Management Software
Facebook it - Tweet it - Print it -
We're here to help you make the most of sysadmin work. So, subscribe!


{ 27 comments… read them below or add one }
Heh, it’s kinda nice feature, since it works, and isn’t something you just think of… I guess most people would block it in a FW…
Thnaks…
Its a temporary solution…
the parmanent one is th find all the ips which acts as an attacker and to use the rule for all.
make a shell script for this.
use netstat to find out max no. of connection by each ip short them out and apply the above rule for all of them.
Nice idea, perhaps something like
route add 65.21.34.4 rejectwill do the same more elegantly?
the reject is not more elegant, it’s better to black hole them certainly for discouraging attackers as they have to wait for a timeout for a response
Gabriele,
The post has been updated. Thanks for pointing out reject option.
Thanks to you for the great site, and please note that, as the man page for route says, “This is NOT for firewalling”.
i tried this
route add 65.21.34.4 gw 127.0.0.1 lo
and it fails on XP with the message
route: bad gateway address gw
same error with this
route add 65.21.34.4 reject
route: bad gateway address gw
copied exactly as you have posted
any ideas ?
James,
These instructions only tested on Linux.
please note that syntaxis is different for the route command from linux to windows, but using the right syntaxis surely it must work.
I think that all we know that this kind of measures are when we are in a hurry, not a definitive solution.
Even though they can be a lifesaver on occasions.
thanks for your work.
by the way …
Does somebody know what is the difference between the use of reject and the use of …. 127.0.0.1 blackhole?
thanks.
reject – send “Network is unreachable” message back to client.
blackhole – No message sent back to client
thanks.. Vivek.
this is important to me, because I have to decide between this two commands.
..say… What would be more adecuate to a hacker?
receive a message saying “network is unreachable” or no message at all?
maybe “network is unreachable”?
or… no message…
I am thinking. Any suggestion?
Carlos: Blackhole is better.
I could not delete the rejected ip with the command given in the tutorial. I’m running Debian.
# route delete 10.0.0.19
SIOCDELRT: No such process
But I was able to delete the rejected ip route with this command:
# route del -host 10.0.0.19 reject
Cheers,
I liked the command used by SeBas to remove the block….
It worked for me:
route del -host 10.0.0.19 reject
got something to learn
So to make this persistent across reboots, what is the syntax for the /etc/sysconfig/network/routes file?
Add commands to /etc/rc.local file.
Thanks Vivek, not the answer I was looking for, but I am sure that would work:)
drop entire subnet
# route add -net 192.67.16.0/24 gw 127.0.0.1 lo
how to enable again?
Its sad how easy it is to forget simple commands like this when you dont use them everyday
Thanks for the blog, saved me a lot of hassle and now null routing works a treat
Damien
Hi,
I want to Block inetnum range IP like 58.208.0.0 – 58.223.255.255 via route add -net command. which command must we use?
Use iptables.
Please give me the iptables usage for that.
Awesome tutorial! But when you reboot routes are erased.
Take a look at ifroute.
Using routing policy database (RPDB) maybe work same!
Try it:
I use this entry in a script.
route add -net 85.90.162.0 netmask 255.255.255.0 reject
But how can I drop this entry without booting my machine?