netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Changli Gao <xiaosuo@gmail.com>
To: Nicola Padovano <nicola.padovano@gmail.com>
Cc: Jan Engelhardt <jengelh@medozas.de>,
	netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: fragmented packet
Date: Mon, 6 Sep 2010 08:09:43 +0800	[thread overview]
Message-ID: <AANLkTi=tx3esVsiFiuHCcL3nxX+7EPfKPwW9ts+MOzqt@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin4Kn5Ueb0QqquoEmSx6abbRtda62=X=NKC4yQU@mail.gmail.com>

On Mon, Sep 6, 2010 at 8:04 AM, Nicola Padovano
<nicola.padovano@gmail.com> wrote:
> those 140 bytes are the __tcp payload__ so the payload of IP is: Ip
> header +TCP payload = 180...
> isn't it?

After checking the code of hping, I find the 'mtu' parameter of hping
is the payload of a IP packet.

So the packet you captured should be 20iphdr + 20tcphdr + 140data,
20tcphdr + 140data == 160("mtu" of hping), no fragmentation is needed.

-- 
Regards,
Changli Gao(xiaosuo@gmail.com)

  reply	other threads:[~2010-09-06  0:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04 17:09 fragmented packet Nicola Padovano
2010-09-04 18:25 ` Jan Engelhardt
2010-09-04 18:31   ` Nicola Padovano
2010-09-04 18:56     ` Nicola Padovano
2010-09-04 22:19 ` Jan Engelhardt
2010-09-04 23:31   ` Nicola Padovano
2010-09-05  9:45     ` Nicola Padovano
2010-09-05 15:24       ` Changli Gao
2010-09-05 15:54         ` Jan Engelhardt
2010-09-05 16:18           ` Changli Gao
2010-09-05 23:19             ` Nicola Padovano
2010-09-05 23:47               ` Changli Gao
2010-09-06  0:04                 ` Nicola Padovano
2010-09-06  0:09                   ` Changli Gao [this message]
2010-09-06  9:51                     ` Nicola Padovano
2010-09-06  0:10                   ` Nicola Padovano
2010-09-06  9:12                     ` Jan Engelhardt

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='AANLkTi=tx3esVsiFiuHCcL3nxX+7EPfKPwW9ts+MOzqt@mail.gmail.com' \
    --to=xiaosuo@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=nicola.padovano@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;
as well as URLs for NNTP newsgroup(s).