Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] meanwhile... .home, finally has a home.arpa.
Date: Tue, 23 Oct 2018 08:09:19 -0700	[thread overview]
Message-ID: <CAA93jw6omcj3Z0c97=OuC=P0VpWW-h_i_sFh_c=YyU0L4z8Nag@mail.gmail.com> (raw)
In-Reply-To: <10E89375-2591-49B2-9A67-AA0E14B17649@fugue.com>

On Mon, Oct 22, 2018 at 9:13 PM Ted Lemon <mellon@fugue.com> wrote:
>
> On Oct 22, 2018, at 11:51 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> This is one of those endless bikesheds I'd totally given up on. Thx ted!
>
>
> If you're feeling like an adventure, you might find the latest draft of the homenet naming architecture entertaining.
>
> https://github.com/ietf-homenet-wg/simple-naming/blob/master/draft-ietf-homenet-simple-naming.txt

Read it just now. this is an ietf notion of "simple", yes?

>
> I decided to keep going on it since the submission deadline was extended, so it's pretty close to feature complete except for the HNCP part.
>
> I'm curious: are you using HNCP on your networks?

Mikael is the sole survivor here, so far as I know.

2 years back, I gave up on deploying ipv6 any further than the lab.
Getting dynamic ipv6 reliably into my production network... I gave up.
I asked for a static allocation from comcast, haven't heard back yet.

As examples that persist, dhcpv6-pd renewals seem to be broken in
openwrt still, so I get a bunch of prefixes... and a few a days later
they vanish. I get static routes to nowhere, often, out of that. And:
with only a /60 available, I also run out of prefixes to allocate if
something reboots at the wrong time at the wrong place, and so on.


>


-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

  reply	other threads:[~2018-10-23 15:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  3:51 Dave Taht
2018-10-23  4:13 ` Ted Lemon
2018-10-23 15:09   ` Dave Taht [this message]
2018-10-23 15:42     ` Ted Lemon
2018-10-23 16:15       ` Dave Taht
2018-10-23 16:44         ` Ted Lemon
2018-10-23 15:47     ` Mikael Abrahamsson
2018-10-23 16:12       ` Dave Taht
2018-10-24  8:22         ` Mikael Abrahamsson
2018-10-24 16:39           ` Dave Taht
2018-10-24 18:04             ` Mikael Abrahamsson
2018-10-23 23:28     ` Michael Richardson
2018-10-23 23:38       ` Dave Taht

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='CAA93jw6omcj3Z0c97=OuC=P0VpWW-h_i_sFh_c=YyU0L4z8Nag@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mellon@fugue.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