81 comment

1. This is a nice breakdown of IPTABLES indeed! Thank you for taking the time for such a comprehensive explaination… I shall bookmark this!

2. Try ferm, “for Easy Rule Making” .

   In file like “ferm.conf” :

   chain ( INPUT OUTPUT FORWARD ) policy DROP;
   chain INPUT proto tcp dport ssh ACCEPT;

   And next:
   ferm -i ferm.conf

   Source: http://ferm.foo-projects.org/

3. Can any one tell me the difference between the DROP vs REJECT? Which one is recommended for my mail server?

   1. LeftMeAlone, “drop” does not send anything to the remote socket while “reject” sending the following message to the remote socket: (icmp destination port unrechable).

      Make clean… “drop” maybe the service does not exists. “reject” you can not access to the service.

4. @LeftMeAlone

   DROP will silently drop a packet, not notifying the remote host of any problems, just won’t be available. This way, they will no know if the port is active and prohibited or just not used.

   REJECT will send an ICMP packet back to the remote host explaining (For the lack of better words) that the host is administratively denied.

   The former is preferred as a remote host will not be able to determine if the port is even up.

   The latter is not recommended unless software requires the ICMP message for what ever reason. Its not recommended because the remote host will know that the port is in use, but will not be able to connect to it. This way, they can still try to hack the port and get into the system,

   Hope this helps!
   Joe

5. thanks !

   help for Iptables…………..

6. Thankssss..

7. how about you try
   host -t a http://www.facebook.com
   a few times, just to see how dns round-rbin works…

8. also, you can try this

   #!/bin/bash
   
   # Clear any previous rules.
   /sbin/iptables -F
   
   # Default drop policy.
   /sbin/iptables -P INPUT DROP
   /sbin/iptables -P OUTPUT ACCEPT
   
   # Allow anything over loopback and vpn.
   /sbin/iptables -A INPUT -i lo -s 127.0.0.1 -d 127.0.0.1 -j ACCEPT
   /sbin/iptables -A OUTPUT -o lo -s 127.0.0.1 -d 127.0.0.1 -j ACCEPT
   /sbin/iptables -A INPUT -i tun0 -j ACCEPT
   /sbin/iptables -A OUTPUT -o tun0 -j ACCEPT
   /sbin/iptables -A INPUT -p esp -j ACCEPT
   /sbin/iptables -A OUTPUT -p esp -j ACCEPT
   
   # Drop any tcp packet that does not start a connection with a syn flag.
   /sbin/iptables -A INPUT -p tcp ! --syn -m state --state NEW -j DROP
   
   # Drop any invalid packet that could not be identified.
   /sbin/iptables -A INPUT -m state --state INVALID -j DROP
   
   # Drop invalid packets.
   /sbin/iptables -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
   /sbin/iptables -A INPUT -p tcp -m tcp --tcp-flags SYN,FIN SYN,FIN              -j DROP
   /sbin/iptables -A INPUT -p tcp -m tcp --tcp-flags SYN,RST SYN,RST              -j DROP
   /sbin/iptables -A INPUT -p tcp -m tcp --tcp-flags FIN,RST FIN,RST              -j DROP
   /sbin/iptables -A INPUT -p tcp -m tcp --tcp-flags ACK,FIN FIN                  -j DROP
   /sbin/iptables -A INPUT -p tcp -m tcp --tcp-flags ACK,URG URG                  -j DROP
   
   # Reject broadcasts to 224.0.0.1
   /sbin/iptables -A INPUT -s 224.0.0.0/4 -j DROP
   /sbin/iptables -A INPUT -d 224.0.0.0/4 -j DROP
   /sbin/iptables -A INPUT -s 240.0.0.0/5 -j DROP
   
   # Blocked ports
   /sbin/iptables -A INPUT -p tcp -m state --state NEW,ESTABLISHED,RELATED --dport 8010 -j DROP
   
   # Allow TCP/UDP connections out. Keep state so conns out are allowed back in.
   /sbin/iptables -A INPUT  -p tcp -m state --state ESTABLISHED     -j ACCEPT
   /sbin/iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -j ACCEPT
   /sbin/iptables -A INPUT  -p udp -m state --state ESTABLISHED     -j ACCEPT
   /sbin/iptables -A OUTPUT -p udp -m state --state NEW,ESTABLISHED -j ACCEPT
   
   # Allow only ICMP echo requests (ping) in. Limit rate in. Uncomment if needed.
   /sbin/iptables -A INPUT  -p icmp -m state --state NEW,ESTABLISHED --icmp-type echo-reply -j ACCEPT
   /sbin/iptables -A OUTPUT -p icmp -m state --state NEW,ESTABLISHED --icmp-type echo-request -j ACCEPT
   
   # or block ICMP allow only ping out
   /sbin/iptables -A INPUT  -p icmp -m state --state NEW -j DROP
   /sbin/iptables -A INPUT  -p icmp -m state --state ESTABLISHED -j ACCEPT
   /sbin/iptables -A OUTPUT -p icmp -m state --state NEW,ESTABLISHED -j ACCEPT
   
   # Allow ssh connections in.
   #/sbin/iptables -A INPUT -p tcp -s 1.2.3.4 -m tcp --dport 22 -m state --state NEW,ESTABLISHED,RELATED -m limit --limit 2/m -j ACCEPT
   
   # Drop everything that did not match above or drop and log it.
   #/sbin/iptables -A INPUT   -j LOG --log-level 4 --log-prefix "IPTABLES_INPUT: "
   /sbin/iptables -A INPUT   -j DROP
   #/sbin/iptables -A FORWARD -j LOG --log-level 4 --log-prefix "IPTABLES_FORWARD: "
   /sbin/iptables -A FORWARD -j DROP
   #/sbin/iptables -A OUTPUT  -j LOG --log-level 4 --log-prefix "IPTABLES_OUTPUT: "
   /sbin/iptables -A OUTPUT  -j ACCEPT
   
   iptables-save > /dev/null 2>&1
   

9. Nice examples, but missing one. Commonly searched rule is one for masquerade.

10. This is extremely useful, somekind of magic and quick recipe…
    (Of course now i can’t send mail on my remote server (to strict rate limit …))

11. Nice examples & thanks.

12. .. I’m anxiously awaiting similar translated to ip6tables. 🙂

13. A most excellent presentation of iptables setup and use. Really Superior work. Thanks kindly.

14. Point 8:

    And for the private address ranges to block on public interfaces, you’ll also want to block

    169.254/16 – zeroconf

15. Nice post, thanks! In example #19 there is an error in the last line:

    ## open access to mysql server for lan users only ##
    iptables -I INPUT -p tcp --dport 3306 -j ACCEPT
    

    Should probably be:

    ## open access to mysql server for lan users only ##
    iptables -I INPUT -p tcp -s 192.168.1.0/24 --dport 3306 -j ACCEPT
    

    1. that is right.

16. Thanks for this post, I hope you don’t mind if I translate this to spanish and post it on my blog, Mentioning the original source, of course.

    Regards

17. Simple rules to share your connection to internet (interface IFNAME) with other hosts on your local LAN (NATTED_SUBNET).
    In other words how to do NAT and MASQEURADEing.

    IFNAME=ppp0
    NATTED_SUBNET=192.168.2.0/24

    # 1) load appropriate kernel module

    modprobe iptable_nat

    # 2) make sure IPv4 forwarding is enabled

    echo 1 > /proc/sys/net/ipv4/ip_forward

    # 3) the appropriate rules

    iptables -A POSTROUTING -t nat -o $IFNAME -s $NATTED_SUBNET -d 0/0 
             -j MASQUERADE
    iptables -A FORWARD -t filter -o $IFNAME -s $NATTED_SUBNET -m state 
            --state NEW,ESTABLISHED,RELATED -j ACCEPT
    iptables -A FORWARD -t filter -i $IFNAME -d $NATTED_SUBNET -m state 
            --state ESTABLISHED,RELATED -j ACCEPT
    

    1. THANKS for this.
       How about blocking a website while having those rules?

18. ## open access to mysql server for lan users only ##
    iptables -I INPUT -p tcp -s 192.168.1.0/24 –dport 3306 -j ACCEPT

    This should be like this:

    -s 192.168.1.0/24 -d 192.168.2.2 -i eth0 -p tcp -m state –state NEW -m tcp –dport 3306 -j ACCEPT

    a rule like this should go under RELATED,ESTABLISHED in the INPUT chain

19. For email servers, I have rate limiting rules in place for all service ports.

    In the INPUT chain I have the spam firewall ip(s), allowed via port 25.

    Then for the email ports, I impose a hit count of 10 in 60 seconds, smart phones, email clients do not poll every second. Anything more than this is dropped and they can continue on a rampage with no affect on the server(s). It took me a while to come up with the rate-limiting chains to work with the email server. Since the Watch Guard XCS devices needed to be exempt from the rules. They have rate-limits on incoming connections as well, a lot better than Barracuda.

    I always specify the source/destination interface, state then the port.

    1. How do i open the port 25 on a public ip (eg. 1.2.3.4) because it is close, I can only send email but can’t receive email?
       But on my localhost it’s open, when I test I able to send and receive only on 127.0.0.1. This is my rule

       iptables -A INPUT -p tcp -m tcp –dport 25 -j ACCEPT

       when i check netstat -tulpn | grep :25
       tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2671/exim4
       tcp6 0 0 ::1:25 :::* LISTEN 2671/exim4

       Hope you can help me on this matter. I really confused on this one.

20. Very useful.
    Thanks

21. Wooooooooooowwwwww. thats coooool…
    very usefull link….

    Thanks yar….

22. Rule #14

    ## *only accept traffic for TCP port # 8080 from mac 00:0F:EA:91:04:07 * ##
    # iptables -A INPUT -p tcp –destination-port 22 -m mac –mac-source 00:0F:EA:91:04:07 -j ACCEPT

    –destination-port 8080 not 22

    Anyway, this is a fu**** good website with fully nice articles.
    Very big thx dudes.

    Happy new year everyone.

23. Excellent Stuff Guys!!!

    Everyone is putting their part. Great to see this kind of community flourish further.

    I am thankful to the ppl who started this website.

24. Excellent thanks.

25. Good info and well written.Easy to understand for everyone… I will be back to learn more needed security rules.. Oh and yes I’m a human but I hate to say the definition of human is ( MONSTER) don’t believe me ? Look it up on the net ! Ha ha ha ha
    Thank you for this page….

26. thank you! for the information on how to delete a firewall rule! priceless! thanks!

27. How can i use iptable rules to use multiple internet connections for the same bit torrent download?
    Actually, i have two broadband connections. I want to combine them. I am told to get load balancing hardware and i cant afford that. So, i did some experimenting. On first DSL modem, i set its IP to be 192.168.1.1
    On second modem, i set its IP to be 192.168.2.1
    Then in windows network adapter settings, i set Metric value of each adapter to 1. Thats about it. My bit torrent downloads/uploads use both my internet connections at the same time which gives effect of combined speed.
    Can i do something like that in Linux?
    Or, how can i combine two internet connections by using iptables? I dont want any hardware changes. All i have is two DSL modems and two network interface cards. Precise help would be greatly appreciated.

28. Hi, got a question to the author of the article. I have tried different kind of commands from the command line, edited the file /etc/sysconfig/iptables directly with following saving and restarting iptables/rebooting system. Nothing helps, my rules get overwritten by the system flushing my new rules or editing them. I tried to open ports (22,21 etc). The goal why I edit my firewall is to get connected to ftp server via FileZilla. Would you recommend me how to open ports? Tell me please if you need any system outputs or something. Cheers

29. > my rules get overwritten by the system flushing my new rules or editing them

    I think you got some sort of script or other firewall product running that is overwriting your rules. Check your cron job and you find the source for the same. If you need further assistance head over to the nixcraft Linux Support forum.

30. thanks for your respond, as I am not a specialist I didn’t any changes to my crontab yet, anyway I checked it, also /cron.d and everything connected to cron in /var/spool/…. Nothing about iptables or something. What I noticed there are several iptables files in /etc/sysconfig/: iptables.old written by system-config-firewall, iptables generated by iptables-save with some changes what I didn’t entered.
    Here is what I entered from wiki.centos.org/HowTos/Network/IPTables:

    # iptables -P INPUT ACCEPT
    # iptables -F
    # iptables -A INPUT -i lo -j ACCEPT
    # iptables -A INPUT -m state –state ESTABLISHED,RELATED -j ACCEPT
    # iptables -A INPUT -p tcp –dport 22 -j ACCEPT
    # iptables -P INPUT DROP
    # iptables -P FORWARD DROP
    # iptables -P OUTPUT ACCEPT
    # iptables -L -v

    Here is what I got in the iptables’s file:

    :INPUT DROP [1:40]
    :FORWARD DROP [0:0]
    :OUTPUT ACCEPT [526:43673]
    -A INPUT -i lo -j ACCEPT
    -A INPUT -m state –state RELATED,ESTABLISHED -j ACCEPT
    -A INPUT -p tcp -m tcp –dport 22 -j ACCEPT
    COMMIT
    Don’t know why it changes, probably it is aplying kind of default settings, but analyzing this settings the port 22 should be open. Nmap says it is closed, telnet outputs connection refused. Was trying to set samba server with the same result due to my firewall. What to do?

31. Thanks a lot for this article, which is extremely easy to understand and follow for beginners as me!

32. Hi
    Regarding the block #7.1: Only Block Incoming Traffic
    The rule
    # iptables -A INPUT -m state –state NEW,ESTABLISHED -j ACCEPT
    looks dubious to me
    Why would you want to allow NEW connections?
    In my view it should read
    # iptables -A INPUT -m state –state RELATED,ESTABLISHED -j ACCEPT

    1. I noticed this as well. The rule as given is not right. I’ve been using iptables for a couple of years now, and the INPUT rule here should read:
       iptables -A INPUT -m state –state ESTABLISHED,RELATED
       (actually the above order is equivalent), because one clearly wouldn’t want to match the NEW state here. Doing so would open up the door to TCP connects (i.e., TCP SYN packets) to any listening TCP services, as well as to UDP datagrams.

       Cheers to the author(s) of nixCraft for a nice article & a useful collection of iptables rules. This has become one of my favorite Linux/Unix blogs, so please keep the articles coming.

33. Thank you very much, this site is very useful. I love all of you.

34. Hi.
    Excellent tutorial. My desire is to block social networking in my job, I did it with squid in transparent mode but skipped to enter https. I did the tests on a virtual pc and it worked fine. The issue is that I is working on the production server. This has two network cards, eth0 traffic where it enters the Internet and eth1 to connect to the network. For the case of Facebook do the following:

    # We block Facebook
    iptables-A OUTPUT-p tcp-d 69.63.176.0/20-dport 443-j DROP
    iptables-A OUTPUT-p tcp-d 66.220.144.0/20-dport 443-j DROP
    iptables-A OUTPUT-p tcp-d 69.171.224.0/19-dport 443-j DROP
    iptables-A OUTPUT-p tcp-d http://www.facebook.com-dport 443-j DROP
    iptables-A OUTPUT-p tcp-d facebook.com-dport 443-j DROP

    Any suggestions?.

    Greetings.

35. really helpful article

36. Hi,

    Here is how to BLOCK FACEBOOK with single line command and iptables:

    for i in $(nslookup facebook.com|grep Address|grep -v “#53″|awk ‘{print $2}’); do iptables -I FORWARD -m tcp -p tcp -d $i/24 –dport 443 -j DROP; done

    You can replace the website with any other secure (https) you want.

    For http websites (non-secure) – use the following line, replacing yahoo.com with the desired domain name:
    for i in $(nslookup yahoo.com|grep Address|grep -v “#53″|awk ‘{print $2}’); do iptables -I FORWARD -m tcp -p tcp -d $i/24 –dport 80 -j DROP; done

    Don’t forget to save your iptables configuration.

    Regards,
    Borislav Bozhanov

37. Thank you!!!

38. Hello.
    I’m working with virtual machines. and would like to make a firewall and rootin bash.

    My question is this
    I have several public ip — IP1 = (200.45.xx.xxx) IP2 (=200.xx), IP3 = ·

    The issue is that one of them use to Wan IP1.

    Now I want to direct traffic from outside to inside. But I also want to redirect the traffic that comes to public ip 2 ( IP2 to the local machine in lan ( 192.168.1.2) and what comes to public ip 3 (IP3) to the local machine (192.168.1.3)

    I can not find examples of how to redirect traffic coming to a specific public IP to a particular LAN private IP.
    If you can ask to help me.

    #!/bin/sh
    
    ## SCRIPT de IPTABLES
    ## Pello Xabier Altadill Izura
    
    echo -n Aplicando Reglas de Firewall...
    
    ## Paramos el ipchains y quitamos el modulo
    /etc/rc.d/init.d/firewall stop
    rmmod ipchains
    
    ## Instalando modulos
    modprobe ip_tables
    modprobe ip_nat_ftp
    modprobe ip_conntrack_ftp
    
    
    ## Variables
    IPTABLES=iptables
    EXTIF="eth1"
    INTIF="eth0"
    
    ## En este caso,
    ## la tarjeta eth1 es la que va al ROUTER y la eth0 la de la LAN
    
    ## Primeras reglas
    /sbin/iptables -P INPUT DROP
    /sbin/iptables -F INPUT
    /sbin/iptables -P OUTPUT ACCEPT
    /sbin/iptables -F OUTPUT
    /sbin/iptables -P FORWARD ACCEPT
    /sbin/iptables -F FORWARD
    /sbin/iptables -t nat -F
    
    ### En principio, si las reglas INPUT por defecto hacen DROP, no haria falta
    ### meter mas reglas, pero si temporalmente se pasa a ACCEPT no esta de mas.
    
    ## Todo lo que viene de cierta IP se deja pasar (administradores remotos…)
    /sbin/iptables -A INPUT -i $EXTIF -s 203.175.34.0/24 -d 0.0.0.0/0 -j ACCEPT
    
    ## El localhost se deja
    /sbin/iptables -A INPUT -i lo -j ACCEPT
    /sbin/iptables -A OUTPUT -o lo -j ACCEPT
    
    ## Aceptar al exterior al 80 y al 443
    
    # Permitir salida al 80
    /sbin/iptables -A INPUT -i $EXTIF -p tcp --sport 80 -j ACCEPT
    /sbin/iptables -A OUTPUT -o $EXTIF -p tcp --dport 80 -j ACCEPT
    # Permitir salida al 443
    /sbin/iptables -A INPUT -i $EXTIF -p tcp --sport 443 -j ACCEPT
    /sbin/iptables -A OUTPUT -o $EXTIF -p tcp --dport 443 -j ACCEPT
    
    ## SALIDA SMTP - Para que el servidor se pueda conectar a otros MTA
    # Permitir salida SMTP
    /sbin/iptables -A INPUT -i $EXTIF -p tcp --sport 25 -j ACCEPT
    /sbin/iptables -A OUTPUT -o $EXTIF -p tcp --dport 25 -j ACCEPT
    
    ## SALIDA FTP - Para que el servidor se pueda conectar a FTPs
    /sbin/iptables -A INPUT -i $EXTIF -p tcp --sport 21 -m state --state ESTABLISHED -j ACCEPT
    /sbin/iptables -A OUTPUT -o $EXTIF -p tcp --dport 21 -m state --state NEW,ESTABLISHED -j ACCEPT
    # ftp activo
    /sbin/iptables -A INPUT -i $EXTIF -p tcp --sport 20 -m state --state ESTABLISHED,RELATED -j ACCEPT
    /sbin/iptables -A OUTPUT -o $EXTIF -p tcp --dport 20 -m state --state ESTABLISHED -j ACCEPT
    # ftp pasivo
    /sbin/iptables -A INPUT -i $EXTIF -p tcp --sport 1024:65535 --dport 1024:65535 -m state --state ESTABLISHED -j ACCEPT
    /sbin/iptables -A OUTPUT -o $EXTIF -p tcp --sport 1024:65535 --dport 1024:65535 -m state --state ESTABLISHED,RELATED -j ACCEPT
    

39. Hi, I have two interfaces: eth0 (for internal network) and eth1 (WAN). The server does the routing to the clients with the following IPtables:

    # Generated by iptables-save v1.4.12 on Fri Oct 19 21:14:26 2012
    *nat
    :PREROUTING ACCEPT [14:1149]
    :INPUT ACCEPT [6:625]
    :OUTPUT ACCEPT [4:313]
    :POSTROUTING ACCEPT [0:0]
    -A POSTROUTING -o eth1 -j MASQUERADE
    COMMIT
    # Completed on Fri Oct 19 21:14:26 2012
    # Generated by iptables-save v1.4.12 on Fri Oct 19 21:14:26 2012
    *filter
    :INPUT ACCEPT [505:53082]
    :FORWARD ACCEPT [0:0]
    :OUTPUT ACCEPT [247:29622]
    -A FORWARD -s 192.168.1.0/24 -i eth0 -o eth1 -m conntrack --ctstate NEW -j ACCEPT
    -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
    COMMIT
    # Completed on Fri Oct 19 21:14:26 2012

    This works fine, however I have no other rules set up. Can anyone help me in deciding what rules I need? the server (who does the NAT) is also running a webserver on port 80, SSH server on 22. All other ports can may be blocked.. how can I achieve this?

    1. I use fwbuilder to create my rules, this interface “looks like” checkpoint’s fw1 client to edit rules. Very graphical, and good to work with.

40. very nice and informative article
    it really helped to work for my VPS server

41. how i do give access ip ex 192.168.0.2 only for facebook .

    1. fb_address=$(dig facebook.com +tcp +short);
       iptables -A OUTPUT -p tcp -s !192.168.0.2/32 -d $fb_address -j DROP;

42. For tip #2, it is advisable to run the -P chain ACCEPt first, before flushing it.
    Exampes
    # iptables -P INPUT ACCEPT
    # iptables -P OUTPUT ACCEPT
    # iptables -P FORWARD ACCEPT
    # iptables -F
    # iptables -t nat -F
    # iptables -X
    #iptables -t nat -X

    Why? If the current chain’s policy is DROP, and you are remotely accessing to the server via SSH, and the rule “-A INPUT -p tcp –dport 22 -j ACCEPT” is still opens the “-P INPUT DROP”. you may disconnected as soon as you flush *-F* the rules, and the default policy “-P INPUT DROP” kicks in. 🙂 If you are working on the local console, it is fine.

    Thank you.

    1. This is a valid point. Another way to avoid locking oneself out, which I have found very useful for testing firewall changes over an SSH session, is the iptables-apply command (incl. with the Ubuntu iptables package for e.g.). It functions essentially the same as the iptables command, but when applying a rule change it prompts w/ a timeout for a confirmation after making the change. If no response is received (in 30 secs. by default), then it rolls back the change (i.e., add, modify, delete or otherwise).

       Once rules have been tested, I save them with iptables-save, and load the stable configuration with an init.d script at system startup (and including support for a ‘restart’ command here, for a clean flush, delete & reapply rules cycle).

43. Could it be you are using iptables save after directly editing? This will overwrite your work. Do a restart to load your newly edited table.

44. Great Thx for awesome site and for awesome reading,tutos.
    Respect And KeepUp dude!

45. from graphical user and groups If I add or delete any user I can’t see any reference log nor in messages or in /var/log/secure file,

    Kindly please advise on this that from GUI if we run/execute any command where does the log message will go.

46. thank you very much for such a wonderful explanation….. very clear and had nice experience with iptables…

47. Hi there,

    i have a problem, i have got a server and LAN network, and this’s feature

    internet (eth0) server (eth1) clients -> 10.0.0.2
    -> 10.0.0.3
    now, i can config to iptables accept all client connect internet, but in this situation, i want to allow only one client (assume: 10.0.0.3), i try but not completed. pls help me 🙂

    Thanks

48. Thanks a lot.

49. Thank you very much. Coincidentally, I just discovered an hour ago that I need to use iptables to allow a tablet computer to talk through my laptop, using the same internet connection. And then I discovered that I can’t remember any of it. I was using IP tables and IP nat 15 years ago, back when it was Darrin Reed’s project (name???), but that was too long ago for my memory. This article will get me back on track fast.
    Thanks again.

50. Module xt_connlimit was disabled. How to limit number of connection per IP, can you module limit and recent. Please help me. 🙂

51. thank you

52. thank you for you ivitation

53. Thank you for this example. I don’t remember the command line off the top of my head and this gives me enough information to do what I need to do without having to read 30 man pages. If only proper support (support.oracle.com) would be so efficient.

54. Enjoyed and appreciated the article and the comments particularly from noone (13 December 2011). I’ve added some of the suggestions to my firewalls.

    The first lines in every INPUT are always

    -A INPUT -s 123.123.123.123/32 -j ACCEPT
    -A INPUT -s 124.124.124.124/32 -j ACCEPT

    123 & 124 represent my external IPs including home and office backup connections.

    These entries ensure that whatever errors I make in IPTables I can never lock myself out of my remote servers.

    Best regards to all,

    Paul.

55. In 7.1, the example provided does not block all incoming traffic like it claims. If you don’t add more parameters, the rule will apply to both directions.

    The example rule:

    iptables -I INPUT -m state –state NEW,ESTABLISHED -j ACCEPT

    This would not only allow for NEW outgoing requests but also NEW incoming requests. The DROP policy for the INPUT chain can’t do it’s job to block incoming connections since it is applied after the rule which allows both NEW incoming and outgoing connections.

56. I have problem when i add by manually (ex: #iptables -A INPUT -s 192.168.0.1 -p tcp –dport 53 -j ACCEP) but when i restart iptables by service iptables restart it not work because :

    1- when i view in /etc/sysconfig/iptables the IP address will be 192.168.0.1/32 but my land /24
    2- problem when i start or stop by system-config-firewall

    Can u help me pls?

57. Hi, I have a question. Could we log packets which are dropped because of forwarding queue is filled (e.g in congestion time)? How do I perform this work?
    Regards Mohammad.

58. Hi there. Greetings from Mexico. Nice examples. Very usefull all of them. But, can I bypass traffic in the port-80 once my iptables-policies are: -P INPUT DROP, -P OUTPUT DROP, -P FORWARD DROP?

    thank you all in advance.

59. How to disable sending back TCP Reset to clients or how to increase TCP reset timeout in iptable.
    (I am using a raw socket as server and able to receive tcp client SYN request, but before sending SYNACK, tcp reset packet is going from server)

60. Hi Guys,

    New to IP Tables, need a little advice – I have a guest wifi network setup, how do I block port 25 outgoing for an ip range?

    Thanks, John Tankard

61. Very nice!

    Thank you!

62. Nice breakdown on iptables!

    However, I prefer (& recommend) to use a firewall manager (command-line / config file based tool) like shorewall:

    http://shorewall.net/

63. Useful page.
    Here’XXX errXXX I found
    #18: Established Connections and >>>Restaring<<< The Firewall

64. Useful page.
    Here’s errtum I found
    #18: Established Connections and >>>Restaring<<< The Firewall

65. iptables -p tcp –syn –dport 80 -m connlimit –connlimit-above 20 –connlimit-mask 24 -j DROP

    I tried above but its not taking through so if am not wrong then it should be as below.

    iptables -A INPUT -p tcp –syn –dport 80 -m connlimit –connlimit-above 20 –connlimit-mask 24 -j DROP

66. The reason why so many poplee use VIM is because it is a text editor that you can use right in the command line and it has so many powerful features. People find that once they get used to using VIM that it is

67. Hello Team,

    Gr8 Iptables notes. Will try & share if found any discripency on command.

    Thanks,

68. you just have to make sure they’re in the correct order. #18: Established Connections and >>>Restaring<<< The Linux Firewall

69. CSF firewall base on iptables is very good for me. I think new SysAdmins should using CSF firewall.

70. Wow. Awesome examples. I loved it. Thanks!!!!!!!!!!!

71. Thanks to all, really this site is excellent to gather knowledge.
    Right now my boss has assigned me a new task. I would like to share this also need to solve the problem. Please help me.
    How to blocked an IP address which is request in my server port (Tomcat) more or equal twenty times per second.
    Suppose my server ip is 123.123.123.123 with it’s port is 80. However, another IP address is concurrently requested in my server. IP address may be different. But, it can be identified by their nature. Per second can attack in my server more that 20 times.

72. can someone put all the recommend lines in one file?
    i see the comments here , and i didn’t get it what to put

73. Hii All,
    Can any one help me for security.
    I want to accept traffic over UDP from particular MAC or device

Comments are closed.