11 comment

  1. Blocking really _ALL_ traffic can cause undesired effects. In fact quite a few applications use the internal loopback interface for internal communication. So the following two rules should be added to allow this:

    iptables -A INPUT -i lo
    iptables -A OUTPUT -o lo

    which allow all traffic via the loopback interface. This should be perfectly safe, even in a hostile environment since all external traffic is still blocked.

  2. Hi all,
    thanks for your input. Unfortunately I don’t know how to extend these commands for a slightly more subtle scenario: I want to prevent users to move server content to the internet (=> iptables -P OUTPUT DROP on that server) but I do want to enable them to move content to the server (e.g., read e-mail, download attachments, …)

    It seems that for general web browsing you do need output traffic (I guess just sending your request string??) but I was hoping that iptables could distinguish between control commands (e.g. sending a HTTP get from the machine to the internet) and actual file transfers from the machine to the internet…

    Is my hope in vain or is there a solution?

    Best regards and thanks in advance,
    Pieter

  3. Hi All,

    I am very new to iptables and new to linux even. I am trying to allow all connections to my eth1 (public interface) except for the traffic coming in and out from udp ports 5060 until 5080 which should be only allowed for specific IP addresses. Here’s my config below:

    iptables –flush
    iptables -P INPUT DROP
    iptables -P FORWARD DROP
    iptables -P OUTPUT DROP
    iptables -A INPUT -i lo -j ACCEPT
    iptables -A OUTPUT -o lo -j ACCEPT
    iptables -A INPUT -s 192.168.0.0/22 -j ACCEPT
    iptables -A OUTPUT -d 192.168.0.0/22 -j ACCEPT
    iptables -A OUTPUT -o eth1 -j ACCEPT

    ###DROP ALL 5060-5080 ports
    #iptables -A INPUT -p udp –dport 5050:5080 -j DROP
    #iptables -A INPUT -p udp –dport 5050:5080 -j DROP

    ###ALLOW ALL PORTS FOR KNOWN IP
    iptables -A INPUT -p udp -s A.B.C.D –dport 5050:5080 -j ACCEPT
    iptables -A INPUT -p udp -s E.F.G.H –dport 5050:5080 -j ACCEPT
    iptables -A INPUT -p udp -s I.J.K.L –dport 5050:5080 -j ACCEPT

    I tested it but I can still connect to that server using the 5061 port using other public ip which is not declared to be allowed.

    Help Please…..

    Thanks

  4. James,

    Not sure if you have got any further with this I’m looking for the same sort solution as my Trixbox was hacked even though I ‘thought’ it was quite secure. I would say that you ought to consider blocking all ports from all IP’s that you do not know, not just the SIP ones.

    Alan…

  5. iptables -A INPUT -s 192.168.0.0/22 -j ACCEPT
    accepts all input from subnets 192.168.0.0, 192.168.1.0, 192.168.2.0 and 192.168.3.0
    iptables -A OUTPUT -d 192.168.0.0/22 -j ACCEPT
    accepts all output from subnets 192.168.0.0, 192.168.1.0, 192.168.2.0 and 192.168.3.0
    you never reach your drop rules
    joe

Leave a Comment