From: Daniel Lezcano <daniel.lezcano@free.fr>
To: Andrian Nord <nightnord@gmail.com>
Cc: lxc-users@lists.sourceforge.net,
Patrick McHardy <kaber@trash.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [Lxc-users] Huge ammount of invalid checksum packets on macvlan
Date: Mon, 21 Feb 2011 17:07:31 +0100 [thread overview]
Message-ID: <4D628DC3.9000400@free.fr> (raw)
In-Reply-To: <20110221153421.GA6602@nord.niifaq.ru>
On 02/21/2011 04:34 PM, Andrian Nord wrote:
> Greetings, Daniel.
>
> On Mon, Feb 21, 2011 at 04:20:59PM +0100, Daniel Lezcano wrote:
>
> 2.6.37 kernel with gentoo linux patches (doesn't affect any low-system
> stuff, AFAIK).
> lxc-0.7.2 is used.
>
> Reproducable on two different machines.
> I'm using tcpdump -vvv for bad checksum detection. This also affects
> traffic from container to hardware node (as it's using macvlan to
> communicate with containers by itself).
>
> Also, I've got same problem on UDP packets coming from lan on other
> server and it was worked around by disabeling tx and rx checksum offload
> via ethtool. But dummy devices doesn't allow this.
I am not sure it is a bug. If we go outside of the container context and
we do the following:
ssh 127.0.0.1
tcpdump -vvv -i lo
We will get the same errors AFAICS.
There is also in the man page the following option:
-K Don't attempt to verify IP, TCP, or UDP checksums. This is useful for
inter‐
faces that perform some or all of those checksum calculation in
hardware; other‐
wise, all outgoing TCP checksums will be flagged as bad.
IMO, the checksum is not needed for the virtual macvlan devices, hence
the checksum is not computed and the checksum tcp packet is not filled.
As the skb's are flagged as 'checksum not necessary' the packets are not
dropped by the kernel and are delivered to the network stack. tcpdump
intercept the raw packet and analyse the header. It will see a bad value
as this one is a default value.
I Cc'ed the netdev mailing list and Patrick in case my analysis is wrong
or incomplete.
Thanks
-- Daniel
next parent reply other threads:[~2011-02-21 16:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110221150710.GA5651@nord.niifaq.ru>
[not found] ` <4D6282DB.2080204@free.fr>
[not found] ` <20110221153421.GA6602@nord.niifaq.ru>
2011-02-21 16:07 ` Daniel Lezcano [this message]
[not found] ` <4D628DC3.9000400-GANU6spQydw@public.gmane.org>
2011-02-21 17:39 ` Huge ammount of invalid checksum packets on macvlan Andrian Nord
2011-02-23 17:13 ` [Lxc-users] Bad checksums and lost packets with macvlan on dummy Andrian Nord
2011-02-24 10:20 ` Daniel Lezcano
2011-02-26 20:38 ` Andrian Nord
2011-02-27 15:14 ` Daniel Lezcano
2011-02-27 19:50 ` Eric Dumazet
2011-02-27 20:35 ` Daniel Lezcano
2011-02-28 7:45 ` [Lxc-users] " Eric Dumazet
2011-03-01 13:29 ` Daniel Lezcano
2011-03-01 16:51 ` Patrick McHardy
2011-03-01 20:04 ` Daniel Lezcano
2011-03-02 11:03 ` Patrick McHardy
2011-03-02 16:03 ` Daniel Lezcano
2011-03-02 18:03 ` Patrick McHardy
2011-03-02 18:33 ` Daniel Lezcano
2011-03-03 14:30 ` Changli Gao
2011-03-08 14:41 ` Patrick McHardy
[not found] ` <4D764030.8020202-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
2011-03-12 21:59 ` Daniel Lezcano
2011-03-12 22:07 ` [Lxc-users] " Daniel Lezcano
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=4D628DC3.9000400@free.fr \
--to=daniel.lezcano@free.fr \
--cc=kaber@trash.net \
--cc=lxc-users@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=nightnord@gmail.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).