From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 218629] New: tc-vlan push vlan is regression from the lab
Date: Fri, 22 Mar 2024 16:02:49 -0700 [thread overview]
Message-ID: <20240322160249.5190c144@hermes.local> (raw)
Begin forwarded message:
Date: Fri, 22 Mar 2024 19:00:46 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 218629] New: tc-vlan push vlan is regression from the lab
https://bugzilla.kernel.org/show_bug.cgi?id=218629
Bug ID: 218629
Summary: tc-vlan push vlan is regression from the lab
Product: Networking
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Other
Assignee: stephen@networkplumber.org
Reporter: ne-vlezay80@yandex.ru
Regression: No
Created attachment 306027
--> https://bugzilla.kernel.org/attachment.cgi?id=306027&action=edit
lab for reproducte the bug
Exec: netns.sh - create test namespaces
Exec: switch.sh - load tc-vlan rule per the namespace
Problem:
tc-vlan regression
Example:
[root@arch user]# ip netns exec host1 iperf3 -c 192.168.1.16
Connecting to host 192.168.1.16, port 5201
[ 5] local 192.168.1.2 port 47824 connected to 192.168.1.16 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 717 MBytes 6.01 Gbits/sec 30 9.97 MBytes
[ 5] 1.00-2.00 sec 736 MBytes 6.17 Gbits/sec 2 9.97 MBytes
[ 5] 2.00-3.00 sec 574 MBytes 4.81 Gbits/sec 0 9.97 MBytes
[ 5] 3.00-4.00 sec 582 MBytes 4.88 Gbits/sec 0 9.97 MBytes
[ 5] 4.00-5.00 sec 687 MBytes 5.76 Gbits/sec 0 9.97 MBytes
[ 5] 5.00-6.00 sec 737 MBytes 6.16 Gbits/sec 3 6.98 MBytes
[ 5] 6.00-7.00 sec 716 MBytes 6.03 Gbits/sec 0 6.98 MBytes
[ 5] 7.00-8.00 sec 705 MBytes 5.92 Gbits/sec 3 4.88 MBytes
[ 5] 8.00-9.00 sec 645 MBytes 5.39 Gbits/sec 0 4.88 MBytes
[ 5] 9.00-10.00 sec 705 MBytes 5.92 Gbits/sec 1 4.88 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 7.01 GBytes 6.02 Gbits/sec 39 sender
[ 5] 0.00-10.00 sec 7.01 GBytes 6.02 Gbits/sec receiver
iperf Done.
[root@arch user]# ip netns exec host1 iperf3 -c 192.168.1.16 -R
Connecting to host 192.168.1.16, port 5201
Reverse mode, remote host 192.168.1.16 is sending
[ 5] local 192.168.1.2 port 60818 connected to 192.168.1.16 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 1.35 GBytes 11.6 Gbits/sec
[ 5] 1.00-2.00 sec 1.42 GBytes 12.2 Gbits/sec
[ 5] 2.00-3.00 sec 1.44 GBytes 12.3 Gbits/sec
[ 5] 3.00-4.00 sec 1.41 GBytes 12.1 Gbits/sec
[ 5] 4.00-5.00 sec 1.40 GBytes 12.0 Gbits/sec
[ 5] 5.00-6.00 sec 1.38 GBytes 11.8 Gbits/sec
[ 5] 6.00-7.00 sec 1.41 GBytes 12.1 Gbits/sec
[ 5] 7.00-8.00 sec 1.41 GBytes 12.1 Gbits/sec
[ 5] 8.00-9.00 sec 1.39 GBytes 12.0 Gbits/sec
[ 5] 9.00-10.00 sec 1.42 GBytes 12.2 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 14.0 GBytes 12.0 Gbits/sec 306 sender
[ 5] 0.00-10.00 sec 14.0 GBytes 12.0 Gbits/sec receiver
iperf Done.
--
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:[~2024-03-22 23:02 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=20240322160249.5190c144@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;
as well as URLs for NNTP newsgroup(s).