From: Philip Craig <philipc@snapgear.com>
To: Laurens van Alphen <subscriptions@keenondots.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: ipt_tcpmss_target: bad length
Date: Mon, 18 Aug 2003 13:03:21 +1000 [thread overview]
Message-ID: <3F4041F9.1030004@snapgear.com> (raw)
In-Reply-To: <269A1D930039744AB5A54123F2D74BCD4A49@dc0.nl.corp.keenondots.net>
Laurens van Alphen wrote:
> Today, I received this kernel log entry via e-mail:
>
> Aug 17 14:19:17 filter0 kernel: ipt_tcpmss_target: bad length (472
> bytes)
>
> Using Google, I could not find a single useful meaning of this message.
Here's the comment from the source code which explains it:
/* Since it passed flags test in tcp match, we know it is is
not a fragment, and has data >= tcp header length. SYN
packets should not contain data: if they did, then we risk
running over MTU, sending Frag Needed and breaking things
badly. --RR */
In other words, SYN packets cannot have data, so the total length
of the packet must be the same as the tcp header length, otherwise
it is a bad length.
--
Philip Craig - philipc@snapgear.com - http://www.SnapGear.com
SnapGear - Custom Embedded Solutions and Security Appliances
prev parent reply other threads:[~2003-08-18 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 17:19 ipt_tcpmss_target: bad length Laurens van Alphen
2003-08-18 3:03 ` Philip Craig [this message]
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=3F4041F9.1030004@snapgear.com \
--to=philipc@snapgear.com \
--cc=netfilter@lists.netfilter.org \
--cc=subscriptions@keenondots.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 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.