From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] ipv6 on comcast with 18.06.1
Date: Mon, 1 Oct 2018 21:07:19 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1810012102290.4550@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw6dvvH6qNUTb0U8RCBeKGVtMKd-fFa=XMimJOzyiCZwKw@mail.gmail.com>
On Mon, 1 Oct 2018, Dave Taht wrote:
> 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....
Looking at your pcap file, there is no IPv6 to be had what so ever. No
answer to RS or DHCPv6 SOLICIT. It doesn't get more basic than that.
> 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! :(
Yes, your problem has nothing to do with basic IPv6 function. Windows
Vista on launch day does the same you're doing, but since nothing is
answering then you get no IPv6. So either your packets aren't making it to
the Comcast upstream router, or it doesn't do any of the basics.
I thought this would be a PD problem or something, but this is more basic
than that.
--
Mikael Abrahamsson email: swmike@swm.pp.se
prev parent reply other threads:[~2018-10-01 19:07 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
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 [this message]
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=alpine.DEB.2.20.1810012102290.4550@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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