From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 90FB23BA8E for ; Mon, 1 Oct 2018 12:45:11 -0400 (EDT) Received: by mail-qt1-x82a.google.com with SMTP id l9-v6so4223712qtf.5 for ; Mon, 01 Oct 2018 09:45:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=PTrg7Ehzs6GxU2PwGRdV46/9hnhM9QF8N4QjTcyJalI=; b=OA9nvd3HS5W2KgPRkWZbet2d1l3KC6VG/A5k17Ctuv2k3+01O4YHTa5R8nK2SitbmF o+H6x8bDtfMRTy0rrkcy//rdxfhWK6NZ5SPeFaDLQoOgsjURvgHSCcgTyk6gK0B18nRQ +ow8szjLYXen1urntJWwcXxE3ypwQ8xXh0mLVOXkkegmwEtprB553gBwtFm889Ixl6JQ biluUl+VcMPngvEz6+yxace1PUel+xfxm53Mbm1+nyy82mdivZi9lrnMWvsS9pLXrBzh UimTexLzJ5erJu3PBDKl5nS2zCFIXG8t0jy+ZggZGIBIg8jUzApbciZJTHo74PlY2wrn VzcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=PTrg7Ehzs6GxU2PwGRdV46/9hnhM9QF8N4QjTcyJalI=; b=FMggMT7haXUFM9H2ENIA9hfUaHitLLBpyoNMrmkxB0vdsoX869olT+lScbsyba5iqK MV6zlIUF+NNFmSFpdRDHiuiIK87MKDb2gwzm/+eeg6Uii6rxq4V6TpKnrKxy4MBsaOQs OrCmpQL6gTc7ZGVE5LVi1tmWjEhzyqxF3k5xPYsVjwBEDYFUT91qCcl6mS78xMMH1hzp oaHeJP9NnUYhzqkUjlDMZqe3F5Nn8bntlZ+Natn0N8OPig9wNKblU4nIl2eTF65/w69H g5w2E+46W+yPDoFkPBhQCk+W9TuDTmkObbvKJmiuT7L50lVUJllRk71hZCujMduvo4FX KNRQ== X-Gm-Message-State: ABuFfogt7dNQXJeXd66lgKRCSQCMLl3SBd5NZYJcvswIa5HlLwvTyka9 E1rU7ig2B0ivPz1EGanDHrsCEFOX5Q1DwTWx0fA= X-Google-Smtp-Source: ACcGV62LNdfCaATewttTlisNHM90OhPqI9t3uwc88N73akTdTQFya8HYnqUUuHxZHnpexqTfRmArPTG8Yiza+PgBB9g= X-Received: by 2002:ac8:21cd:: with SMTP id 13-v6mr9353062qtz.171.1538412311090; Mon, 01 Oct 2018 09:45:11 -0700 (PDT) MIME-Version: 1.0 References: <20181001162951.mt4dguv46axm5i5g@angus.ind.wpi.edu> In-Reply-To: <20181001162951.mt4dguv46axm5i5g@angus.ind.wpi.edu> From: Dave Taht Date: Mon, 1 Oct 2018 09:44:59 -0700 Message-ID: To: Chuck Anderson Cc: Mikael Abrahamsson , cerowrt-devel@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 16:45:11 -0000 On Mon, Oct 1, 2018 at 9:29 AM Anderson, Charles R wrote: > > Is udp checksum offload enabled? If so, tcpdump/wireshark won't see > the actual checksum and assume it is bad. I imagine it is theoretically offloaded. I DO have an 18.06.1 arm box now up that IS getting dhcpv6-pd from comcast.... This arm box IS getting dhcpv6-pd from comcast correctly. root@gw1:~# cat /etc/openwrt_release DISTRIB_ID=3D'OpenWrt' DISTRIB_RELEASE=3D'18.06.1' DISTRIB_REVISION=3D'r7258-5eb055306f' DISTRIB_TARGET=3D'ipq806x/generic' DISTRIB_ARCH=3D'arm_cortex-a15_neon-vfpv4' DISTRIB_DESCRIPTION=3D'OpenWrt 18.06.1 r7258-5eb055306f' DISTRIB_TAINTS=3D'' My mips and x86_64 boxes aren't. Otherwise based on my 4+ year old memory of this stuff, I don't see anything immediately wrong with the solicit. (I updated the bug, too) > > On Mon, Oct 01, 2018 at 09:12:57AM -0700, Dave Taht wrote: > > hmm... bad udp checksum??? > > > > :/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 wrote: > > > > > > On Mon, Oct 1, 2018 at 8:58 AM Dave Taht wrote: > > > > > > > > Here you go! Going to go look at the firewall rules in a sec.... > > > > > > I changed the rules to allow 547 and 546, no difference. I even > > > flushed the ipv6tables rules entirely, > > > and I'm running without that for a while. I can certainly imagine > > > comcast's dhcpv6 server giving up on me.... > > > > > > It's nice to know, btw, someone is still messing with homenet. Having > > > zero funding for > > > too many years burned me out on even trying. But I expected ipv6 to > > > keep working without > > > any more help from me! :( > > > > > > > On Mon, Oct 1, 2018 at 8:45 AM Mikael Abrahamsson wrote: > > > > > > > > > > On Mon, 1 Oct 2018, Dave Taht wrote: > > > > > > > > > > > Sigh. Once upon a time I used to test this stuff on comcast. So= I > > > > > > finally got around to deploying > > > > > > a new 18.06 gateway and ipv6 is busted with comcast. > > > > > > > > > > Can you please email me output from "tcpdump -n -vvv -i por= t 546 or > > > > > port 547 or icmp6" as your WAN is trying to get DHCPv6-PD ? Or if= you dump > > > > > that to a pcap and email it to me (or make it available somewhere= for me > > > > > to download). > > > > > > > > > > I have 18.06.1 working with homenet on WRT1200AC,dual uplinks (tw= o > > > > > different vlans on WAN), getting dual stack from both ISPs, /56 f= rom both, > > > > > and both are announced out on LAN. I even configured bidirectiona= l SQM > > > > > with CAKE on each uplink (250/50 and 250/100 respectively) and it= seems to > > > > > do the right thing. --=20 Dave T=C3=A4ht CEO, TekLibre, LLC http://www.teklibre.com Tel: 1-669-226-2619