Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
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 15:30:46 +0100	[thread overview]
Message-ID: <87eh20lwx5.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw4dL54ShO0my-isbMvAriMcfnzmacxz5yE9KOPHgmGq9g@mail.gmail.com> (Dave Taht's message of "Mon, 17 Mar 2014 06:40:01 -0700")

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

Dave Taht <dave.taht@gmail.com> writes:

> At least one blueray player we know of isn't working through the
> default dhcp/dns/upnp setup.

Why would a bluray player need upnp? *shudder*

> I've modeled  something that basically should  work in my bcp38 repo.

So, not sure exactly how it's supposed to work; does this hook into the
firewall after NAT'ing has been applied? Otherwise you'd presumably need
to add exceptions for the configured internal network(s)? (I think that
may be what is going on in the bcp script at ln 38, but some sort of
auto-detection of the relevant network(s) would be needed? Or as a
minimum a whitelist configuration option?)

Could double-nat be detected from wan iface hotplug or somesuch?

> That said, surviving an ipv6 renumber is a problem. Many clients
> probably don't respect an address assignment lifetime.

Application-transparent MPTCP from the operating system with automatic
failover? Pretty please? :)

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2014-03-17 14:30 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 [this message]
2014-03-17 14:39       ` Toke Høiland-Jørgensen
2014-03-17 14:55       ` Dave Taht
2014-03-17 14:55     ` Michael Richardson
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=87eh20lwx5.fsf@toke.dk \
    --to=toke@toke.dk \
    --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