From: Vlad Yasevich <vyasevich@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: SCTP PMTU calculation not accounting chunk padding.
Date: Wed, 09 Sep 2015 20:39:57 +0000 [thread overview]
Message-ID: <55F0991D.6080509@gmail.com> (raw)
On 09/09/2015 03:00 AM, Deepak Khandelwal wrote:
> Hi,
>
>
> It looks like the PMTU calculation in SCTP kernel / RFC, seems to be not
> accounting the chunk padding
>
>
> SCTP calculate the fragmentation point to fragment the packet.
>
>
>
> Frag_point = PMTU – (sctp header length + sctp chunk length) – IP header
> length
>
>
>
> After the frag_point, user data fragmentation happens at SCTP layer, but
> while sending packet due the need of chunk padding, data size still more
> then mtu of in between router, and packet doesn’t pass through to the
> channel . local SCPT stack always end up receiving the ICMP FRAG _NEEDED
> messages.
>
> I am using Kernel version 2.6.34.9-WR4.3
>
You are missing
commit c08751c851b78514f6ec5f77f7cbebaac63d15c0
Author: Alexander Sverdlin <alexander.sverdlin@nsn.com>
Date: Mon Sep 2 15:58:25 2013 +0200
net: sctp: Fix data chunk fragmentation for MTU values which are not multiple of 4
-vlad
> Thanks !
> Best Regards,
> Deepak
>
reply other threads:[~2015-09-09 20: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=55F0991D.6080509@gmail.com \
--to=vyasevich@gmail.com \
--cc=linux-sctp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.