From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 6F4533B260 for ; Fri, 17 Jun 2016 10:21:38 -0400 (EDT) Received: by mail-oi0-x230.google.com with SMTP id u201so119162965oie.0 for ; Fri, 17 Jun 2016 07:21:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=2kZrlIaxiNjHPnbq6ktfp6Ky4pvoWc2FP5/RE+ChNik=; b=me+A1d3KNUtS/0zO9a1hr+wQNJX5LXApWhEivHJafPw9YLZgGC45I8SwTi7zDETGdX QcGlWaR/FxVr2J/Lwg85nW71HAbp9DFC9RI84ThhcWx1Cq1jIu9fDsEQl90pk8Ypwen/ sFSnXZ56ZgdM1EWwnUtZZB1KRze9mAEQEjF24+VYjEHgPnxJ0Kmd+Obw6VvUrJ/EK74/ hEYrvjeUJQ6Yime4EoSBaRlhy1kWIiO+FwXPXsOc6XIMJu5IdIM2MRP7RdCdoWO+EObo gJeU8J9Ne1cBkDrESXRdW77NsNZcad+WU2wQiOAE8sdb2+k0HCxziH2py7uRgyLRt795 DMQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=2kZrlIaxiNjHPnbq6ktfp6Ky4pvoWc2FP5/RE+ChNik=; b=Yy+KgkWjGaUvf63NUS43KWLqGR13FvO+fSJ7KPmXc+373SBicsL2vYJflRhwyCPtfa hB01uhF4axOlMnsRbh1DDyYmHgd6ZUXpHS5QtiMz2usS602qQtxONtY04Zje2FXxwtIF aoBMjdmguRCyhEQWNyVc6wGuRt8RZtQyDe81fLWs/imsNMBPp0zB/muwKtIHoGHU3bJz gKRhhqbOsA52A+hEgTO0mTDLP5sYw9KUdEEMKSWEip5WZ8ZdNiT981ai1hgqLb7RTKR7 lsGnB/v3x+XJK8h/vSSia+h4rN7qvcbu7HWk5P96p624XR6rCjeOA7T76LhQm38fT2pN PGqQ== X-Gm-Message-State: ALyK8tKuxZEZzyB+T29niAIU0tD69HHR9OoP0ssRa6RW44FT2RMxZYif9+nhXvm6koARTfPzS6DaT096k2ZJvA== X-Received: by 10.202.190.8 with SMTP id o8mr1527702oif.152.1466173297740; Fri, 17 Jun 2016 07:21:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.175.130 with HTTP; Fri, 17 Jun 2016 07:21:37 -0700 (PDT) In-Reply-To: References: From: Dave Taht Date: Fri, 17 Jun 2016 07:21:37 -0700 Message-ID: To: Simon Dalley Cc: "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cerowrt-devel] [Bloat] ipv6 not quite working for me on internal networks 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: Fri, 17 Jun 2016 14:21:38 -0000 On Thu, Jun 16, 2016 at 8:56 PM, Simon Dalley wrot= e: > Hello, > > First, thanks for all the work to make cerowrt what it is. Was. I am really encouraging everyone to update to lede at this point, which has nearly everything that was "good" about cerowrt in it. > I am having some difficulty with ipv6 on the "last hop", namely my intern= al > network. > > Platform: Netgear WNDR3800 > Cerowrt version: CeroWrt Toronto 3.10.50-1 / LuCI Trunk (svn-r10459) > > AQUISS, my UK ISP, provides an ipv6 address range: > IPv6 Address 20xx:xxxx:xx55:ae00::/56 Are you getting this via dhcp-pd or is it static? > Recommended MTU: 1458 bytes > > I can make ipv6 work when connecting PC host "centaur" directly to the ca= ble > modem and running pppd. ping6 ipv6.google.com etc works fine. The "cable" modem is running over ppp??? > > Reconnecting via the WNDR3800, everything ipv4 related works fine with > "centaur" on the se00 subnet. > > I can also ping6 without problems from the WNDR3800: > root@cerowrt:~# ping6 ipv6.google.com > PING ipv6.google.com (2a00:1450:4009:80f::200e): 56 data bytes > 64 bytes from 2a00:1450:4009:80f::200e: seq=3D0 ttl=3D53 time=3D15.576 = ms > 64 bytes from 2a00:1450:4009:80f::200e: seq=3D1 ttl=3D53 time=3D14.959 = ms > 64 bytes from 2a00:1450:4009:80f::200e: seq=3D2 ttl=3D53 time=3D15.156 = ms > 64 bytes from 2a00:1450:4009:80f::200e: seq=3D3 ttl=3D53 time=3D15.044 = ms > ^C > --- ipv6.google.com ping statistics --- > 4 packets transmitted, 4 packets received, 0% packet loss > round-trip min/avg/max =3D 14.959/15.183/15.576 ms > > but ping6 can't get through from centaur on se00: A traceroute6 would be better. Try it from various source addresses on the router. Disabling the firewall for ipv6 is sometimes helpful also, for debugging. You might also want a reqprefix of 56 in the wan stanza. We did not have much chance to test against any other prefix sizes than 64, 60, and 48. > root@centaur:/etc/network# ping6 ipv6.google.com > PING ipv6.google.com(lhr25s02-in-x200e.1e100.net) 56 data bytes > From lhr25s02-in-x200e.1e100.net icmp_seq=3D1 Destination unreachable: = No > route > From lhr25s02-in-x200e.1e100.net icmp_seq=3D2 Destination unreachable: = No > route > From lhr25s02-in-x200e.1e100.net icmp_seq=3D3 Destination unreachable: = No > route > From lhr25s02-in-x200e.1e100.net icmp_seq=3D4 Destination unreachable: = No > route > ^C > --- ipv6.google.com ping statistics --- > 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time > 3024ms > > For your information, ipv6 routes on centaur are: > root@centaur:/etc/network# ip -6 route > 20xx:xxxx:xx55:ae10::f48 dev eth0 proto kernel metric 256 expires > 84847sec pref medium > 20xx:xxxx:xx55:ae10::/64 dev eth0 proto ra metric 100 pref medium > 20xx:xxxx:xx55:ae00::/56 via fe80::2cb0:5dff:fea6:94ad dev eth0 proto = ra > metric 100 pref medium > fe80::/64 dev eth0 proto kernel metric 256 pref medium > default via fe80::2cb0:5dff:fea6:94ad dev eth0 proto static metric 10= 0 > pref medium > > and on the router are: > root@cerowrt:~# ip -6 route > default from :: via fe80::f60f:1bff:fe17:8d00 dev pppoe-ge00 proto sta= tic > metric 1024 > default from 20:xx:xxxx:xx00:55ae::/64 via fe80::f60f:1bff:fe17:8d00 de= v > pppoe-ge00 proto static metric 1024 you should also have had a default from 20xx:xxxx:xx55:ae00::/56 I think. ip -6 route add default from > 20xx:xxxx:xx55:ae00::/64 dev gw00 proto kernel metric 256 > 20xx:xxxx:xx55:ae01::/64 dev gw10 proto kernel metric 256 > 20xx:xxxx:xx55:ae02::/64 dev sw00 proto kernel metric 256 > 20xx:xxxx:xx55:ae03::/64 dev sw10 proto kernel metric 256 > 20xx:xxxx:xx55:ae10::/60 dev se00 proto kernel metric 256 This appears wrong to me in that ae10 should have been a /64 > unreachable 20xx:xxxx:xx55:ae00::/56 dev lo proto static metric > 2147483647 error -128 > fe80::/64 dev se00 proto kernel metric 256 > fe80::/64 dev ifb0 proto kernel metric 256 > fe80::/64 dev sw10 proto kernel metric 256 > fe80::/64 dev sw00 proto kernel metric 256 > fe80::/64 dev gw10 proto kernel metric 256 > fe80::/64 dev gw00 proto kernel metric 256 > fe80::/64 dev ge00 proto kernel metric 256 > fe80::/10 dev pppoe-ge00 metric 1 > fe80::/10 dev pppoe-ge00 proto kernel metric 256 > > I'm stumped. Can anybody help? > > regards, Simon > > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > --=20 Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org