From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mcr@sandelman.ca>
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id A45BF3BA8E
 for <cerowrt-devel@lists.bufferbloat.net>;
 Mon,  1 Oct 2018 13:13:32 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21])
 by tuna.sandelman.ca (Postfix) with ESMTP id 01FA820090;
 Mon,  1 Oct 2018 13:13:31 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179)
 id 9FA9A1537; Mon,  1 Oct 2018 13:13:31 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1])
 by sandelman.ca (Postfix) with ESMTP id 9C9F73D6;
 Mon,  1 Oct 2018 13:13:31 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
cc: Mikael Abrahamsson <swmike@swm.pp.se>, cerowrt-devel@lists.bufferbloat.net
In-Reply-To: <CAA93jw67meaOWsL5BAk8uxYwn9DyFQCSK78N8Lk8mLc5mTOEYg@mail.gmail.com>
References: <CAA93jw5iiR9nTj3VrSkKNRRBX2LmiCikXTBfsek2GV=u4Hartw@mail.gmail.com>
 <alpine.DEB.2.20.1810011740430.4550@uplift.swm.pp.se>
 <CAA93jw4WvWDpcvGiz2wbr9CvD0tfr=BygpeXx=7rz+7pmhzo2g@mail.gmail.com>
 <CAA93jw6dvvH6qNUTb0U8RCBeKGVtMKd-fFa=XMimJOzyiCZwKw@mail.gmail.com>
 <CAA93jw67meaOWsL5BAk8uxYwn9DyFQCSK78N8Lk8mLc5mTOEYg@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;
 <'$9xN5Ub#
 z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
 micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 01 Oct 2018 13:13:31 -0400
Message-ID: <32226.1538414011@localhost>
Subject: Re: [Cerowrt-devel] ipv6 on comcast with 18.06.1
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
 <cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
 <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
 <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2018 17:13:32 -0000

--=-=-=
Content-Type: text/plain


Dave Taht <dave.taht@gmail.com> wrote:
    > hmm... bad udp checksum???

With some capture mechanisms, tcpdump gets bogus values because the hardware
did the checksums.  I wouldn't imagine that we have hardware checksum offload
on openwrt devices, but could be.

Or it's a real issue.

    > :/tmp# 09:12:17.404257 IP6 (flowlabel 0xdfff4, hlim 1, next-header UDP
    > (17) payload length: 159) fe80::20d:b9ff:fe43:a06c.546 > ff02::1:2.547:
    > [bad udp cksum 0x58f4 -> 0xc4a1!]  On Mon, Oct 1, 2018 at 9:12 AM Dave
    > Taht <dave.taht@gmail.com> wrote:

Did you capture with -i device, or -i any?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAluyVbsACgkQgItw+93Q
3WUuKAgAtNiqsbx1UXB4w6QyWRvMMo2s4yCicrWHLrAx0FwbjDsXPKcKpKEih3kW
tT+gv2ELe0yMqQTvZc4lsf65tpaWia0uTrmGpNCrYN+DoDYmumR1SfYrBlzGGvWY
UyslhdDxMi8AAvxVzoVddvg1SlAbnFvC/3B2uQ6xGV54Ujt9gLuniiYK07hDLIv+
knzKr2kgh6AzL9nxyfVpjbmkxjxYTq/m/FwQxDpGWxA3zBuUC/dmqd97HSd6Zth1
UvzrCvBoDrhBnoqkvaJZ2/zrhxNG4+90xZbvG/MbVmDlEPAdnwdxXLdun9aWXFf/
p56DReeABYB+SHdI5KioReAE5Z91cw==
=5INK
-----END PGP SIGNATURE-----
--=-=-=--