From: "Torsten Lüttgert" <t.luettgert@cbxnet.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Stephen Hemminger <shemminger@osdl.org>, yoshfuji@linux-ipv6.org
Subject: Re: incorrect checksum on sent TCP-MD5 packets (2.6.20-rc5)
Date: Tue, 16 Jan 2007 11:40:48 +0100 [thread overview]
Message-ID: <1168944048.3033.14.camel@sokrates.cff> (raw)
In-Reply-To: <20070115101522.481e2f8f@freekitty>
On Mo, 2007-01-15 at 10:15 -0800, Stephen Hemminger wrote:
> Are you running over a device that does checksum offload?
Ooh, I'm feeling stupid now. Yes, I was. Turns out the problem
are the md5 checksums after all. Crypto-enabled tcpdump says:
11:05:42.856702 IP (tos 0x0, ttl 64, id 35129, offset 0, flags [DF],
proto: TCP (6), length: 80) 212.87.33.4.60565 > 212.87.49.254.bgp: S,
cksum 0x4a03 (correct), 1122127063:1122127063(0) win 5840 <mss
1460,sackOK,timestamp 63686126 0,nop,wscale 5,nop,nop,md5:valid>
11:05:42.871809 IP (tos 0x0, ttl 253, id 0, offset 0, flags [none],
proto: TCP (6), length: 64) 212.87.49.254.bgp > 212.87.33.4.60565: S,
cksum 0x0cc9 (correct), 2943414712:2943414712(0) ack 1122127064 win
16384 <mss 516,md5:valid,eol>
11:05:42.872085 IP (tos 0x0, ttl 64, id 35130, offset 0, flags [DF],
proto: TCP (6), length: 60) 212.87.33.4.60565 > 212.87.49.254.bgp: .,
cksum 0x4160 (correct), ack 1 win 5840 <nop,nop,md5:valid>
11:05:42.872150 IP (tos 0x0, ttl 64, id 35131, offset 0, flags [DF],
proto: TCP (6), length: 105) 212.87.33.4.60565 > 212.87.49.254.bgp: P,
cksum 0x54ec (correct), 1:46(45) ack 1 win 5840 <nop,nop,md5:invalid>:
BGP, length: 45
...
- Torsten
prev parent reply other threads:[~2007-01-16 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 19:32 incorrect TCP " Torsten Luettgert
2007-01-15 18:15 ` Stephen Hemminger
2007-01-16 10:40 ` Torsten Lüttgert [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=1168944048.3033.14.camel@sokrates.cff \
--to=t.luettgert@cbxnet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®