public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 214241] New: System freezes after redirect traffic from bridge interface
Date: Tue, 31 Aug 2021 08:55:01 -0700	[thread overview]
Message-ID: <20210831085501.4f7d6c3b@hermes.local> (raw)

This looks like a user error. Since bridge takes Ethernet packets
and PPP use different header encapsulation. Perhaps kernel could check for this?

Begin forwarded message:

Date: Tue, 31 Aug 2021 14:01:51 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 214241] New: System freezes after redirect traffic from bridge interface


https://bugzilla.kernel.org/show_bug.cgi?id=214241

            Bug ID: 214241
           Summary: System freezes after redirect traffic from bridge
                    interface
           Product: Networking
           Version: 2.5
    Kernel Version: 5.13.13
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: ne-vlezay80@yandex.ru
        Regression: No

If redirecting traffic on bridge interface to ppp interface, system it's
freezes.

tc qdisc add dev bridge0 handle 1: root htb default 1

tc filter add dev bridge0 parent 1: flower src_mac 88:00:42:42:00:aa dst_mac
88:00:42:42:00:ab action vlan eth_pop action mirred egress redirect dev ppp0



after send traffic, system it's freezes.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-08-31 15:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210831085501.4f7d6c3b@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@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