[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZaEzpWaTLDG6Ofby@nanopsycho>
Date: Fri, 12 Jan 2024 13:42:13 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH iproute2-next 1/4] man: get rid of
doc/actions/mirred-usage
Thu, Jan 11, 2024 at 07:44:08PM CET, stephen@...workplumber.org wrote:
>The only bit of information not already on the man page
>is some of the limitations.
>
[...]
>diff --git a/man/man8/tc-mirred.8 b/man/man8/tc-mirred.8
>index 38833b452d92..71f3c93df472 100644
>--- a/man/man8/tc-mirred.8
>+++ b/man/man8/tc-mirred.8
>@@ -94,6 +94,14 @@ interface, it is possible to send ingress traffic through an instance of
> .EE
> .RE
>
>+.SH LIMITIATIONS
>+It is possible to create loops which will cause the kernel to hang.
Hmm, I think this is not true for many many years. Perhaps you can drop
it? Anyway, it was a kernel issue.
>+Do not have the same packet go the same netdevice twice in a single graph of policies.
>+.PP
>+Do not redirect for one IFB device to another.
>+IFB is a very specialized case of packet redirecting device.
>+Redirecting from ifbX->ifbY will cause all packets to be dropped.
>+
> .SH SEE ALSO
> .BR tc (8),
> .BR tc-u32 (8)
>--
>2.43.0
>
>
Powered by blists - more mailing lists