From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-9 released
Date: Mon, 17 Mar 2014 10:55:39 -0400 [thread overview]
Message-ID: <5620.1395068139@sandelman.ca> (raw)
In-Reply-To: <CAA93jw4dL54ShO0my-isbMvAriMcfnzmacxz5yE9KOPHgmGq9g@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> wrote:
>> Dave Taht <dave.taht@gmail.com> wrote:
>> > - haven't tried blue-ray
>>
>> quai?
> At least one blueray player we know of isn't working through the
> default dhcp/dns/upnp setup.
okay, I was imaging you plugging a blue-ray player onto the USB port...
and then... ... ? profit.
>> > items were procd support
>> > for babeld, and bcp38 support. We have issues still with upnp. hnetd,
>>
>> is bcp38 support something you are expecting to see in the UI scripts or is
>> there some other place that you'd expect to see it?
> firewall and UI support would be good
> I've modeled something that basically should work in my bcp38 repo.
>> while we need to drop packets from ULA src at the *WAN* edge, I am wondering
>> how we deal with a gentle renumber from the ISP... I'm thinking that we
>> should just leave all the prefixes that PD gave us in place for some time.
>> Maybe LRU on 16 prefixes...
> With source specific routing for ipv6 we have no need for bcp38 for ipv6.
well... if all of our tables are source specific, then I guess I agree.
If we have no default route for a default source, then we have implemented bcp38.
> It's needed for ipv4.
That's a different can of worms.
The NAT table won't survive a renumber...
> That said, surviving an ipv6 renumber is a problem. Many clients probably
> don't respect an address assignment lifetime.
I have experimental evidence that it's the opposite: clients give up their
address and on-linkness way too easily.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2014-03-17 14:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 19:58 Dave Taht
2014-03-16 21:27 ` Valdis.Kletnieks
2014-03-16 21:45 ` Dave Taht
2014-03-17 0:03 ` Toke Høiland-Jørgensen
2014-03-17 0:42 ` Valdis.Kletnieks
2014-03-17 0:54 ` Dave Taht
2014-03-17 12:20 ` Michael Richardson
2014-03-17 13:40 ` Dave Taht
2014-03-17 14:30 ` Toke Høiland-Jørgensen
2014-03-17 14:39 ` Toke Høiland-Jørgensen
2014-03-17 14:55 ` Dave Taht
2014-03-17 14:55 ` Michael Richardson [this message]
2014-03-17 15:18 ` Dave Taht
2014-03-18 10:00 ` Török Edwin
2014-03-18 12:12 ` Sebastian Moeller
2014-03-18 14:21 ` Dave Taht
2014-03-18 15:22 ` Török Edwin
2014-03-18 15:35 ` Dave Taht
2014-03-18 16:49 ` Török Edwin
2014-03-18 17:03 ` Dave Taht
2014-03-18 17:06 ` Valdis.Kletnieks
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=5620.1395068139@sandelman.ca \
--to=mcr@sandelman.ca \
--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