From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] ipv6 on comcast with 18.06.1
Date: Mon, 1 Oct 2018 09:12:01 -0700 [thread overview]
Message-ID: <CAA93jw6dvvH6qNUTb0U8RCBeKGVtMKd-fFa=XMimJOzyiCZwKw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4WvWDpcvGiz2wbr9CvD0tfr=BygpeXx=7rz+7pmhzo2g@mail.gmail.com>
On Mon, Oct 1, 2018 at 8:58 AM Dave Taht <dave.taht@gmail.com> 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 <swmike@swm.pp.se> 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 <wan> port 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 (two
> > different vlans on WAN), getting dual stack from both ISPs, /56 from both,
> > and both are announced out on LAN. I even configured bidirectional SQM
> > with CAKE on each uplink (250/50 and 250/100 respectively) and it seems to
> > do the right thing.
> >
> > --
> > Mikael Abrahamsson email: swmike@swm.pp.se
>
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-10-01 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 15:30 Dave Taht
2018-10-01 15:45 ` Mikael Abrahamsson
2018-10-01 15:58 ` Dave Taht
2018-10-01 16:12 ` Dave Taht [this message]
2018-10-01 16:12 ` Dave Taht
2018-10-01 16:29 ` Anderson, Charles R
2018-10-01 16:44 ` Dave Taht
2018-10-01 17:13 ` Michael Richardson
2018-10-01 17:22 ` Dave Taht
2018-10-01 19:07 ` Mikael Abrahamsson
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6dvvH6qNUTb0U8RCBeKGVtMKd-fFa=XMimJOzyiCZwKw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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