From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 107551] New: IPV4 Reassembling Problem
Date: Mon, 9 Nov 2015 10:40:01 -0800 [thread overview]
Message-ID: <20151109104001.09d86030@xeon-e3> (raw)
Begin forwarded message:
Date: Mon, 9 Nov 2015 11:04:29 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 107551] New: IPV4 Reassembling Problem
https://bugzilla.kernel.org/show_bug.cgi?id=107551
Bug ID: 107551
Summary: IPV4 Reassembling Problem
Product: Networking
Version: 2.5
Kernel Version: 4.2.3
Hardware: Other
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: bernd.weiberg@siemens.com
Regression: No
I have an ipv4 reassembling issue using the latest Kernel (4.2.3) in an nios2
environment.
I first noticed that issue when sending UDP-Pakets from an Host PC to my
device. Each packet has a payload of 4096 Byte.
Due to the MTU of 1500 Byte each packet will be split into three ip-packets.
Approximately 1 of 200 Packets were not correctly
reassembled by the Kernel, so they cannot be received within user-space. The
command nstat says, that there are reassembling errors
due to timeout, but at least in wireshark all packets are correctly displayed.
Sometime the kernel issues a icmp-messages, saying that there
was a timeout during ip reassembling.
I fir9st thought that it might be a performance problem, so I increased the
time between the packets to about one packet per 500 ms but without success.
Then I decided to reduce the payload to 1024 Byte, because it might be a buffer
(or TSE FIFO) problem. Now all packets are send into one ipv4 packet and there
is nothing lost on the receiver side, but when I reduced the MTU of the host
from 1500 to 800 byte (each datagram will be split into two packets now) the
problem accurse again!
So this might be a reassembling issue.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-11-09 18:39 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=20151109104001.09d86030@xeon-e3 \
--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).