≡ Menu

Linux Iptables Avoid IP Spoofing And Bad Addresses Attacks

Spoofing and bad address attack tries to fool the server and try to claim that packets had come from local address/network.

Following IP/netwok address are know to open this kind of attack:

Incoming source IP address is your servers IP address

Bad incoming address from following ranges:

  • Your own internal server/network ip address/ranges.

Following small shell script tries to prevent this kind of attacks:

INT_IF="eth1" # connected to internet 
SERVER_IP="" # server IP
LAN_RANGE="" # your LAN IP range 
# Add your spoofed IP range/IPs here
IPT="/sbin/iptables" # path to iptables
# default action, can be DROP or REJECT 
# Drop packet that claiming from our own server on WAN port
# Drop packet that claiming from our own internal LAN on WAN port
## Drop all spoofed 
for ip in $SPOOF_IPS
 $IPT -A INPUT -i $INT_IF -s $ip -j $ACTION
 $IPT -A OUTPUT -o $INT_IF -s $ip -j $ACTION
## add or call your rest of script below to customize iptables ##

Save and close the file. Call above script from your own iptables script. Add following line to your /etc/sysctl.conf file

The net.ipv4.conf.all.rp_filter=1 entry enables source address verification which is inbuilt into Linux kernel itself and last two lines logs all such spoofed packets in log file.

Share this on:

{ 19 comments… add one }

  • Prerak Doshi November 23, 2006, 7:30 am

    How to configure squid as a direct connection?
    I would like to following option enable through squid
    1. Username password security with individual site Blocking security.
    2. FTP, SMTP, POP3 etc.. protocol and port configure.
    3. Cache configuration
    4. log maintenance of internet usage, bad site request, downloading, uploading with user name.
    5. firewall configuration to block intruders.(Apart from local user nobody outside the LAN can use our port and connection to the internet
    6. Antivirus : Clamav

  • nixCraft November 23, 2006, 9:20 am


    You are using Red hat Linux…..????

  • Ash December 28, 2006, 4:38 pm

    – iptables -A INPUT -s -j DROP
    + iptables -A INPUT -s $ip -j DROP

  • nixCraft December 28, 2006, 6:04 pm


    PHP treated $ip as PHP variable. But now it is fixed.

    Appreciate your post.

  • budi August 6, 2007, 11:39 pm

    Address is used by server mail or other server like dns or /etc/hosts. And if was blocked the server no running, how solve it?

  • Muhammad Kamran Azeem April 10, 2008, 4:16 pm

    I think that the following code:,

    # Original code – Start
    # Add your IP range/IPs here,
    iptables -A INPUT -s $SERVER_IP -j DROP
    for ip in $SPOOF_IPS
    iptables -A INPUT -s $ip -j DROP
    # Original Code – End

    , can be re-written as :-

    # Suggested Code – Start
    # Add your IP range/IPs here,
    for ip in $SPOOF_IPS
    iptables -A INPUT -i $PUBLICIF -s $ip -j DROP

    # Suggested code – Stop

    Please correct me if I am wrong, but IMHO, if we DROP packets without mentioning the interface then legitimate connections originating from the same server on loopback (lo) will also get dropped.


    • Cody July 26, 2014, 12:52 pm

      lo is a different interface and is not related to outgoing packets. That’s why it is called the loopback interface. lo should always be accepted for INPUT and OUTPUT. That’s regardless of state; indeed, it is for local connections only (and by local I mean Not allowing lo is going to break a lot of services and otherwise cause unexpected results.

  • Muhammad Kamran Azeem April 10, 2008, 5:29 pm

    Sorry. This line:-

    Should not contain $SERVER_IP and should instead be:-


  • Gunjan July 9, 2008, 6:35 am

    Yes we need to be remove $SERVER_IP from SPOOF_IPS other wise server also block and we do not have any access to server

  • nixCraft July 9, 2008, 11:21 am


    The script has been updated to only filter on public interface. This should fix the issue.

  • kwik August 4, 2008, 7:20 pm

    It is impossible to spoof your address if your Linux computer is behind NAT enabled router such as Cisco.

    This script is more useful on *Linux based router* as packet filtering is one defense against IP spoofing attacks. The Linux gateway to a network usually performs ingress filtering, which is blocking of packets from outside the network with a source address inside the network. This prevents an outside attacker spoofing the address of an internal machine. Ideally the Linux gateway would also perform egress filtering on outgoing packets, which is blocking of packets from inside the network with a source address that is not inside. This prevents an attacker within the network performing filtering from launching IP spoofing attacks against external machines.

    I hope this will help someone.

  • Shoelaces November 5, 2011, 3:35 am

    I had to comment out:

    this wouldn’t allow SSH connections out

  • Jouni "Rautamiekka" Järvinen August 6, 2012, 1:07 pm

    What about when the computer doesn’t have a LAN address, like those directly connected to Internet ?

  • Jouni "Rautamiekka" Järvinen August 6, 2012, 2:20 pm

    And why manually specify IPtables path when you can use §`which iptables`§ instead ?

  • shahzaib January 21, 2013, 11:46 am


    Please if you can guide me about how can i identify if someone spoofing to my ip ? Which logs should i check ?

  • chadwick March 12, 2013, 5:30 am

    How do you “call this script from iptables”. What does that mean?

  • RealityBoy August 30, 2013, 11:36 am

    How do you “call this script from iptables”. What does that mean?

  • Bharath September 26, 2013, 9:26 am

    hi, my Linux Email Server(centos 5.7) is giving IP Address Spoofing in N/W.
    am not running any proxy server in that. kept firewall off. now port 25 smtp is giving ip address spoofing with server’s public ip.

    please advice.

  • Cody July 26, 2014, 12:57 pm

    Something comes to mind (and I admit I’ve been awake since 2 this morning, but…):

    /sbin/iptables -A OUTPUT -o eth1 -s -j DROP

    seems highly suspect to me. If eth1 is the interface connected to the Internet that also has the IP bound to it, then you’re blocking outgoing traffic. Note the OUTPUT chain. The point of blocking spoofed packets and in particular the specific public IP(s) the server (or depending on network: firewall, …) is incoming packets. Outgoing packets would naturally have your node’s IP address, after all (unless we’re talking spoofing and/or not wanting your traffic forwarded by routers, potentially even your ISP’s router [like your default gateway]). It is hosts that are NOT you that are claiming to be you. Your server SHOULD send outbound as its IP (NOT to itself) but should not be sending packets TO itself FROM its IP (that should be blocked).

Leave a Comment

   Tagged with: , , , , , , , ,