https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #21 from Keyong ---
Many thanks to all provide helps!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Richard Scheffenegger changed:
What|Removed |Added
Status|Open|In Progress
Prio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #20 from Richard Scheffenegger ---
This behavior was likely introduced by 0533fab89e37caab886568df88d9f939e85eeb6c
D28634 (Mar 25 2021), but addressed with
c21b7b55bea2cc2bf3b420c70a9018e703ed6f00 D36046 (Aug 31 2022).
Looking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Michael Zhilin changed:
What|Removed |Added
CC||miz...@freebsd.org
Seve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #18 from Richard Scheffenegger ---
For completeness, the awk script with proper indexing:
cat output | awk '
//{
fr=int($5/1448);
if ((fr*1448 == $5) && (fr > 0)) {
print $1" "$2" "$3" "$4" "$5"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Richard Scheffenegger changed:
What|Removed |Added
Status|New |Open
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #17 from Richard Scheffenegger ---
1448 byte chunks between server and client align perfectly until server frame
#51 (5 chunks: 0xb23ee730dd0xc2fd29b2eb0xbe27bbf1be0xb829e51fdc
0xbc5b20682b) and client frame #48 (
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #16 from Richard Scheffenegger ---
My script was not using correctly calculating the index when extracting the
payload bytes (vs. nibbles).
Server:
2 10.234.1.9 35249 229 15928 11
0x71d1c76e360xb735f725570xbad512b35a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #15 from Michael Tuexen ---
Is it possible to test if the problem does still exists in stable/13?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #13 from Keyong ---
(In reply to Hans Petter Selasky from comment #12)
Thanks for your information.
The client Linux kernel was not the lastest.
With the SACK disabled I haven't reproduce this issue. Only can reproduce this
issu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #11 from Keyong ---
(In reply to Richard Scheffenegger from comment #10)
Yes, the capture created before issuing the read.
Because the issue was not reproduced 100%, so need to capture with a long time,
the origin packet was to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256820
Koichiro Iwao changed:
What|Removed |Added
CC||h...@freebsd.org
--- Comment #8 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #10 from Richard Scheffenegger ---
There seems to be a discrepancy in the TSO vs LRO payload bytes (maybe my
script is broken?):
Server:
2 10.234.1.9 35249 229 15928 11
72053392291 38571493459141963220672940103156
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #9 from Richard Scheffenegger ---
ClientSide:
2 10.234.1.9 35249 229 11584 8
72053392291 385714934591419632206729401031568921410043220839
398170924830381008236919388657879560
3 10.234.1.9 46833 229 4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #8 from Keyong ---
(In reply to Richard Scheffenegger from comment #5)
Thanks for your detail analyze, sorry to forget attach the client side packet
trace, attached both sides now.
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #7 from Keyong ---
Created attachment 237477
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=237477&action=edit
Server side packet trace
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Keyong changed:
What|Removed |Added
Attachment #235649|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #5 from Richard Scheffenegger ---
Where are the two independent packet traces, if you traced on both client and
server at the same time?
Also, disabling SACK will lead to much worst packet loss recovery performance,
while also
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #4 from Keyong ---
(In reply to Richard Scheffenegger from comment #2)
The packet captured on both client and server.
During the last reproduce this issue, the client/server LRO/TSO with default
setting, I didn't change that.
T
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #3 from Keyong ---
(In reply to Gleb Smirnoff from comment #1)
The freeBSD deployed on the physical machine.
The software used to send the data is "truenas".
Thanks
Keyong
--
You are receiving this mail because:
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #2 from Richard Scheffenegger ---
Can you please provide more context around the traces?
Did you capture on the client side, or on the server side?
It appears, that the capture was performed on the client side, with LRO enabled
23 matches
Mail list logo
