From: Stephen Reese <rsreese@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: tc egress mirror to tunnel causing hard lock
Date: Fri, 05 Jan 2018 04:20:54 +0000 [thread overview]
Message-ID: <CAC6_mQNcBdT2qTdZX2POP=sKneTrHG0k8w3VbHgfLaP7M5MPGw@mail.gmail.com> (raw)
Wanted to follow-up in order to determine if someone might have
thoughts on why applying the following causes a virtual guest to
freeze:
tc filter add dev ens33 parent 100: \
protocol all \
u32 match u8 0 0 \
action mirred egress mirror dev tun0
Experiencing symptoms in several VPS providers.
On Fri, May 12, 2017 at 1:43 PM, Stephen Reese <rsreese@gmail.com> wrote:
> When I apply an egress mirror to a GRE or VXLAN tunnel, the Linux host
> locks up requiring a hard restart. I have tried Ubuntu and Debian. The
> ingress snippet works fine. I can apply the ingress and egress
> statements to a dummy or second real interface and everything works so
> it seems to be an issue with tunnels. Am I missing something or is
> this expected behavior?
>
> ip tunnel add tun0 mode gre remote 172.20.0.6 local 172.20.0.10 ttl 255
> ip link set tun0 up
> ip addr add 192.168.0.2/24 dev tun0
>
>
> # Ingress
> tc qdisc add dev ens33 ingress
> tc filter add dev ens33 parent ffff: \
> protocol all \
> u32 match u8 0 0 \
> action mirred egress mirror dev tun0
>
> # Egress
> tc qdisc add dev ens33 handle 100: root prio
> # The following causes the system to lock up if applied to a tunnel,
> in this case tun0
> tc filter add dev ens33 parent 100: \
> protocol all \
> u32 match u8 0 0 \
> action mirred egress mirror dev tun0
next reply other threads:[~2018-01-05 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 4:20 Stephen Reese [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-12 17:43 tc egress mirror to tunnel causing hard lock Stephen Reese
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC6_mQNcBdT2qTdZX2POP=sKneTrHG0k8w3VbHgfLaP7M5MPGw@mail.gmail.com' \
--to=rsreese@gmail.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).