From 3b16c8fe2ef61e682bc9d867f3e6049fe2fa6173 Mon Sep 17 00:00:00 2001 From: david Date: Sat, 3 Aug 2019 15:38:21 +0000 Subject: Added a comment: Firewall.flush needed? --- .../comment_3_f9fb0a214ee8bc4fac11c3c16747cbe2._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/How_to_make_P.Property.Firewall.rule_persistent/comment_3_f9fb0a214ee8bc4fac11c3c16747cbe2._comment (limited to 'doc') diff --git a/doc/forum/How_to_make_P.Property.Firewall.rule_persistent/comment_3_f9fb0a214ee8bc4fac11c3c16747cbe2._comment b/doc/forum/How_to_make_P.Property.Firewall.rule_persistent/comment_3_f9fb0a214ee8bc4fac11c3c16747cbe2._comment new file mode 100644 index 00000000..ad4bad4a --- /dev/null +++ b/doc/forum/How_to_make_P.Property.Firewall.rule_persistent/comment_3_f9fb0a214ee8bc4fac11c3c16747cbe2._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="david" + avatar="http://cdn.libravatar.org/avatar/22c2d800db6a7699139df604a67cb221" + subject="Firewall.flush needed?" + date="2019-08-03T15:38:21Z" + content=""" +A simple(-minded) solution to the problem with ip-tables-save is to provide a way to invoke \"iptables -F\". It seems like this is needed in general, just to have a known starting point. At least most examples of setting up a firewall with iptables start by flushing the existing rules. +"""]] -- cgit v1.2.3