summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPhil Sutter <phil@nwl.cc>2022-12-03 22:44:40 +0100
committerPhil Sutter <phil@nwl.cc>2022-12-14 15:45:47 +0100
commit92ce78d04677d4d1b6d0144bed6e50180adc7d82 (patch)
tree131e857b3e264d3fa86aaba7a6b79fd29faa8d06
parentbf8bc21b5d0fb386bb14019ebe7ebab6dd85cdef (diff)
Drop INCOMPATIBILITIES file
The problems described in there were relevant 17 years ago. Signed-off-by: Phil Sutter <phil@nwl.cc>
-rw-r--r--INCOMPATIBILITIES14
1 files changed, 0 insertions, 14 deletions
diff --git a/INCOMPATIBILITIES b/INCOMPATIBILITIES
deleted file mode 100644
index ddb24087..00000000
--- a/INCOMPATIBILITIES
+++ /dev/null
@@ -1,14 +0,0 @@
-INCOMPATIBILITIES:
-
-- The REJECT target has an '--reject-with admin-prohib' option which used
- with kernels that do not support it, will result in a plain DROP instead
- of REJECT. Use with caution.
- Kernels that do support it:
- 2.4 - since 2.4.22-pre9
- 2.6 - all
-
-- There are some issues related to upgrading from 1.2.x to 1.3.x on a system
- with dynamic ruleset changes during runtime. (Please see
- https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=334).
- After upgrading from 1.2 to 1.3, it suggest go do an iptables-save, then
- iptables-restore to ensure your dynamic rule changes continue to work.