aboutsummaryrefslogtreecommitdiffstats
path: root/package/network
diff options
context:
space:
mode:
authorJo-Philipp Wich <jow@openwrt.org>2013-03-08 15:27:33 +0000
committerJo-Philipp Wich <jow@openwrt.org>2013-03-08 15:27:33 +0000
commit50213fc3541c6871e541f492ced763263f430dfe (patch)
tree66ab1892ab3fad7998886ebbf3d8b24da77b81c2 /package/network
parent39a001dc697dd421022d801c438976302598900c (diff)
downloadupstream-50213fc3541c6871e541f492ced763263f430dfe.tar.gz
upstream-50213fc3541c6871e541f492ced763263f430dfe.tar.bz2
upstream-50213fc3541c6871e541f492ced763263f430dfe.zip
firewall3: update to git head
- introduce per-zone user chains - support legacy "tcpudp" protocol notation SVN-Revision: 35903
Diffstat (limited to 'package/network')
-rw-r--r--package/network/config/firewall3/Makefile4
-rw-r--r--package/network/config/firewall3/files/firewall.user3
2 files changed, 5 insertions, 2 deletions
diff --git a/package/network/config/firewall3/Makefile b/package/network/config/firewall3/Makefile
index cd9405eae4..e29f614637 100644
--- a/package/network/config/firewall3/Makefile
+++ b/package/network/config/firewall3/Makefile
@@ -8,13 +8,13 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=firewall3
-PKG_VERSION:=2013-03-02
+PKG_VERSION:=2013-03-08
PKG_RELEASE:=$(PKG_SOURCE_VERSION)
PKG_SOURCE_PROTO:=git
PKG_SOURCE_URL:=git://nbd.name/firewall3.git
PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION)
-PKG_SOURCE_VERSION:=46536e5263c4bf57a91c38b5d08d78c774649dda
+PKG_SOURCE_VERSION:=b2b2e69b19a20a46f3db6d717a899248fa24628c
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION)-$(PKG_SOURCE_VERSION).tar.gz
PKG_MAINTAINER:=Jo-Philipp Wich <jow@openwrt.org>
diff --git a/package/network/config/firewall3/files/firewall.user b/package/network/config/firewall3/files/firewall.user
index 1ccbd01657..6f799063f5 100644
--- a/package/network/config/firewall3/files/firewall.user
+++ b/package/network/config/firewall3/files/firewall.user
@@ -2,3 +2,6 @@
# Put your custom iptables rules here, they will
# be executed with each firewall (re-)start.
+# Internal uci firewall chains are flushed and recreated on reload, so
+# put custom rules into the root chains e.g. INPUT or FORWARD or into the
+# special user chains, e.g. input_wan_rule or postrouting_lan_rule.