summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBart De Schuymer <bdschuym@pandora.be>2002-07-25 14:55:14 +0000
committerBart De Schuymer <bdschuym@pandora.be>2002-07-25 14:55:14 +0000
commit4c4447d85b6c84c3da21c8f70650abffdf7b33ec (patch)
treecacfa5b56262603eecdfbdb19c4060551d4ca06d
parentb26649e7813ae62c90504ea5e8befc0590465c82 (diff)
update --xxxx--target RETURN comments
-rw-r--r--ebtables.86
1 files changed, 3 insertions, 3 deletions
diff --git a/ebtables.8 b/ebtables.8
index f67142a..e28b9dd 100644
--- a/ebtables.8
+++ b/ebtables.8
@@ -490,7 +490,7 @@ knows what to do.
The default target is ACCEPT. Making it CONTINUE could let you use
multiple target extensions on the same frame. Making it DROP doesn't
make sense, but you could do that too. RETURN is also allowed. Note
-that using RETURN in a base chain will result in the CONTINUE behaviour.
+that using RETURN in a base chain is not allowed.
.TP
.B dnat
The
@@ -516,7 +516,7 @@ The default target is ACCEPT. Making it CONTINUE could let you use
multiple target extensions on the same frame. Making it DROP only makes
sense in the BROUTING chain but using the redirect target is more logical
there. RETURN is also allowed. Note
-that using RETURN in a base chain will result in the CONTINUE behaviour.
+that using RETURN in a base chain is not allowed.
.TP
.B redirect
The
@@ -535,7 +535,7 @@ knows what to do.
The default target is ACCEPT. Making it CONTINUE could let you use
multiple target extensions on the same frame. Making it DROP in the
BROUTING chain will let the frames be routed. RETURN is also allowed. Note
-that using RETURN in a base chain will result in the CONTINUE behaviour.
+that using RETURN in a base chain is not allowed.
.TP
.B mark
The mark target can be used in every chain of every table. It is possible