From: Patrick McHardy <kaber@trash.net>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
netdev@vger.kernel.org,
Netfilter Developer <netfilter-devel@lists.netfilter.org>
Subject: Re: sky2 hw csum failure [was Re: sky2 large MTU problems]
Date: Thu, 25 May 2006 13:15:39 +0200 [thread overview]
Message-ID: <447591DB.2020901@trash.net> (raw)
In-Reply-To: <6278d2220605250355y316f974cl216f22d198475666@mail.gmail.com>
Daniel J Blueman wrote:
> On 25/05/06, Patrick McHardy <kaber@trash.net> wrote:
>
>> Daniel, is there an easy way to reproduce the checksum failure?
>
>
> In short, no. This was seen when packets may have been truncated by
> large MTU (eg 9000) problems in the sky2 driver transmit path.
>
> There is a small chance that this could relate to transmitting with an
> MTU of 9000 (possibly with receiving with an MTU of 1500 too)
Unfortunately I can't test this myself because my other NICs don't
support MTUs > 1500.
> On that interface, the only rules that were being exercised were:
>
> iptables -t filter -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -t filter -A INPUT -p tcp -m tcp --dport 445 --syn -j ACCEPT # SMB
> iptables -t filter -A INPUT -j DROP
That shouldn't cause any packet modifications. Can you trigger the
checksum failures without netfilter?
next prev parent reply other threads:[~2006-05-25 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6278d2220605240228v576dd66atdad4855b308e64bf@mail.gmail.com>
2006-05-24 17:38 ` sky2 hw csum failure [was Re: sky2 large MTU problems] Stephen Hemminger
2006-05-25 9:17 ` Daniel J Blueman
2006-05-25 10:35 ` Patrick McHardy
2006-05-25 10:55 ` Daniel J Blueman
2006-05-25 11:15 ` Patrick McHardy [this message]
2006-05-30 9:10 ` Daniel J Blueman
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=447591DB.2020901@trash.net \
--to=kaber@trash.net \
--cc=daniel.blueman@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).