Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Justin Madru <justin.jdm64@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] DLNA with wired and wireless devices
Date: Fri, 18 Jan 2013 11:32:53 -0500	[thread overview]
Message-ID: <CAA93jw4tLtTo1qj+Hu6K5gCdqYFatH3z5FczoqhWX4bwkPDK+w@mail.gmail.com> (raw)
In-Reply-To: <CAJ5gi5Ki8B0Onz8q=Ac6=X1X1PjhtfRbapfoLQnKYAg=osLJ4w@mail.gmail.com>

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

On Fri, Jan 18, 2013 at 12:36 AM, Justin Madru <justin.jdm64@gmail.com>wrote:

> Awesome! It seems to be working now. Thanks!
>

OK, so to me this means that routing in the home, rather than bridging, can
work even with upnp and dlna. Which makes me happy as I hope to one day be
able to explore the effect of bridging gigE and wireless in larger scale
networks. I have plenty of raw data showing how bad an idea it is, but
nothing comprehensive as yet.

A core question for me then becomes, how does upnp deal with multiple
routers in the home, if they aren't natted?

Another item is that upnp has the ability to advertise the available
bandwidth to clients, and I was thinking of storing the rate limiting for
ceroshaper in that rather that in a dedicated file. Does anything actually
use that information? What do common bittorrent clients do with upnp
nowadays? How about skype?

Are there any other common gateway applications that are going to break in
a routed environment?

-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 1548 bytes --]

  reply	other threads:[~2013-01-18 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16  9:32 Justin Madru
2013-01-16 19:02 ` Maciej Soltysiak
2013-01-17 19:55 ` Maciej Soltysiak
2013-01-18  5:36   ` Justin Madru
2013-01-18 16:32     ` Dave Taht [this message]
2013-01-18 18:45       ` dpreed
2013-01-18 19:01         ` 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=CAA93jw4tLtTo1qj+Hu6K5gCdqYFatH3z5FczoqhWX4bwkPDK+w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=justin.jdm64@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