From: Nishit Shah <nsshah.82@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: TSO issue - DNAT/mark based routing/MASQUEARDE on locally genrated traffic
Date: Thu, 4 Jun 2009 20:01:18 +0530 [thread overview]
Message-ID: <b2d58cb80906040731oce8cc42k8dd42f1f396fc16f@mail.gmail.com> (raw)
Hi,
Whenever there is a output device change for locally
generated traffic due to,
DNAT/mark based routing in OUTPUT nat/mangle
MASQURADE in POSTROUTING nat
NETIF_F_TSO flag is not unset from sk->sk_route_caps.
So, there are chances that, output device returned at TCP/IP layer
routing supports NETIF_F_TSO and changed output device due to
DNAT/mark based routing/MASQUERADE doesn’t support NETIF_F_TSO.
In some of my experiments for some interfaces, I got “NETDEV_WATCHDOG:
eth1 transmit timeout” messages and for some others packets doesn’t go
out of the box.
Currently I have disabled TSO on all interfaces through ethtool.
Is there any other way to solve this issue (something like resetting
the flag in route_me_harder() if device doesn’t support TSO ) ?
Rgds,
Nishit Shah.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2009-06-04 14:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b2d58cb80906040731oce8cc42k8dd42f1f396fc16f@mail.gmail.com \
--to=nsshah.82@gmail.com \
--cc=netfilter-devel@vger.kernel.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).