From: Eric Dumazet <eric.dumazet@gmail.com>
To: Omar Alhassane <oalhassane@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: PROBLEM: Fragmentation issue with 1521 bytes ip packets
Date: Tue, 15 May 2012 17:04:19 +0200 [thread overview]
Message-ID: <1337094259.8512.1100.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAPFXtPexGpVyGGuKdjpuH+cxOaxa7KeBfmFrs39=NW7LsZ6-bw@mail.gmail.com>
On Tue, 2012-05-15 at 10:00 -0400, Omar Alhassane wrote:
> Hello Folks,
>
> I think i may have found a problem with the linux networking stack.
> Below is a description of the problem.
>
> [1.] One line summary of the problem:
> No response to pings of certain sizes.
>
> [2.] Full description of the problem/report:
> Using hping3, when i ping a linux machine with 1521 bytes ip packets i
> get only one response.
> But when i use 1482 bytes, everything works fine. I've tried this with
> both tcp and udp. The MTU of my interface is 1500.
> [3.] Keywords (i.e., modules, networking, kernel):
> ip, udp, tcp, networking, fragmentation
> [4.] Kernel version (from /proc/version):
> 3.3.1
> [5.] Output of Oops.. message (if applicable) with symbolic information
> [6.] A small shell script or example program which triggers the
> problem (if possible)
> The following commands works only if the target has tcp port 22 open
>
> hping3 -d 1481 -S -P 22 10.0.30.225 (only one response)
> hping3 -d 1482 -S -P 22 10.0.30.225 (works fine)
>
> Can somebody confirm if this is a problem?
hping3 bug : All the fragments it sends have the same ID field.
First 2 frags are reassembled by remote. Remote sends a SYNACK.
Following frags are 'ignored' because they have same ID than previous
packet.
next prev parent reply other threads:[~2012-05-15 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 14:00 PROBLEM: Fragmentation issue with 1521 bytes ip packets Omar Alhassane
2012-05-15 15:04 ` Eric Dumazet [this message]
2012-05-16 19:36 ` Omar Alhassane
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=1337094259.8512.1100.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oalhassane@gmail.com \
/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