From: Denys Fedoryschenko <denys@visp.net.lb>
To: romieu@fr.zoreil.com, netdev@vger.kernel.org
Subject: r8169, enabling TX checksumming breaks things?
Date: Wed, 23 Sep 2009 09:15:27 +0300 [thread overview]
Message-ID: <200909230915.27854.denys@visp.net.lb> (raw)
Hi
Is it expected that:
1)TX checksumming is off by default
2)If i try to enable it over ethtool -K eth0 tx on , TCP sessions on proxy
getting stuck, even in tcpdump looks everything fine and packets reaching
destination, i don't understand what is a reason of failure.
Maybe if this feature supposed to not work - user must not be able just to
turn it on?
Checksum OFF, connection established, no data received.
www.nuclearcat.com/files/r8169_tx_off.txt
Checksum ON, connection established, no data received.
www.nuclearcat.com/files/r8169_tx_on.txt
If required i can capture binary pcap files.
next reply other threads:[~2009-09-23 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 6:15 Denys Fedoryschenko [this message]
2009-09-23 14:02 ` r8169, enabling TX checksumming breaks things? David Dillow
2009-09-23 14:24 ` Denys Fedoryschenko
2009-09-24 1:12 ` David Dillow
2009-09-25 23:18 ` Denys Fedoryschenko
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=200909230915.27854.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).