Simple script, allows to manage docker published ports in IPTABLES the same way as local published ports.

All filtering happens in mangle table: allowed, denied and rejected packets are marked. In INPUT and OUTPUT chains packets are accepted, dropped or rejected by flag set.

This makes setup simple, straightforward and easy to manage. See examples in iptables directory.

git clone https://github.com/freepaddler/ssdfw
sudo cp ssdfw/ssdfw.sh /usr/local/bin
sudo cp ssdfw/iptables/ssdfw.rules /etc/iptables/

Place rules in:

• /etc/iptables/ssdfw.rules
• /etc/iptables/ssdfw.d/*.rules
• if no of these files found, rules are applied from script itself (yes, they may be also managed)

Run ssdfw.sh without args to apply rules. Script will try to use 'iptables-apply' (if found) to be failsafe.

Subcommands (1st arg):

• show show all ssdfw rules (iptables -S)
• list list all ssdfw rules (iptables -L)
• flush delete ssdfw rules, allow in and out
• flush_iptables delete all iptables rules, allow in and out

Find rules examples in iptables directory.

Since ssdfw.sh is just a shell script, working with iptables, then most directives are just vars and functions declared in script itself.

You can easily use original iptables commands to add custom rules.

Add DNAT rules

• table: nat

• chain: PREROUTING

• directive $nat_in to add rule to the section

• targets:

  • any IPTABLES supported targets (commonly DNAT)

Filters traffic to host itself (including DNATed ports for docker). Use instead of filter INPUT

• table: mangle
• chain: PREROUTING
• directive $in to add rule to the section
• first match target applied (allow, deny, reject, ignore)
• custom targets:
  • check-state: special directive, MUST exist in IN section at least once
    • it ACCEPTs ESTABLISHED and RELATED packets
    • it checks packet destination, if destination is not host itself, then IN processing stops and packet enters IP FORWARD section
  • allow = ACCEPT
  • deny = DROP
  • reject = REJECT (with-reset for tcp)
  • ignore = leave chain without allow/deny decision
  • skip: skip next matching rule for this packet

skip target allows to mark packet to skip next matching rule. designed to be used for straightforward exclusion. The example below excludes 10.0.12/0 and 10.1.2.3 from dropping by deny -d 10/8 rule.

$in -j skip -d 10.0.12/0
$in -j skip -d 10.1.2.3
$in -j deny -d 10/8

Filters forwarded traffic (not dedicated to host itself), excluding DNATed ports (docker). Use instead of filter FORWARD

• table: mangle
• chain: FORWARD
• directive $fwd to add rule to the section
• first match target applied (allow, deny, reject, ignore)
• custom targets:
  • allow = ACCEPT
  • deny = DROP
  • reject = REJECT (with-reset for tcp)
  • ignore = leave chain without allow/deny decision
  • skip: skip next matching rule for this packet

Filter host outgoing traffic

• table: filter

• chain: OUTPUT

• directive $out to add rule to the section

• targets:

  • any IPTABLES supported targets (ACCEPT, DROP...)

Manage SNAT and MASQUERADING

• table: nat

• chain: POSTROUTING

• directive $nat_in to add rule to the section

• targets:

  • any IPTABLES supported targets (SNAT, MASQUERADE)

I don't deal much with ipv6, that's why script does nothing with it. But some may use no_ipv6 directive

• no_ipv6 DROP all ipv6 traffic, allowing only lo interface
• no_ipv6 --allow-out additionally allows any outgoing traffic

• works with bridged docker interfaces (docker+, br-+)
• docker swarm mode is not tested

apk add iptables
ssdfw.sh
rc-service iptables save
rc-service ip6tables save
rc-update add iptables 
rc-update add ip6tables
rc-service iptables start
rc-service ip6tables start