Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Luis E. Garcia" <luis@bitamins.net>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] USB3 or HDMI ethernet? - Are wires dead?
Date: Mon, 18 Apr 2016 09:14:32 -0700	[thread overview]
Message-ID: <CALnBQ5=X8+1nvggYbY-cpTrQq8e5UGCfANPsw+ycFq0Yh2=mXg@mail.gmail.com> (raw)
In-Reply-To: <8381.1460995710@obiwan.sandelman.ca>

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

I agree with Michael - wired Ethernet is very stable  compared with
Wireless.
In crowed places where everyone has a WiFi router - the WiFi will
experience random drops.
There is the inconvenient of cabling the place up - but the stability is
very much worth it - but I've using PowerLine adapters to ease my way
through for a couple of years now and they've always proven more reliable
than WiFi - but they do tend to have a bandwidth cap.

Luis
Let´s agree to disagree.

On Mon, Apr 18, 2016 at 9:08 AM, Michael Richardson <mcr@sandelman.ca>
wrote:

> Dave Taht <dave.taht@gmail.com> wrote:
>     > But it asks a question - if basic wifi-only + compute has fallen so
>     > low, is ethernet dead? Every TV I've seen has both ethernet and
> wifi, I
>     > have no idea what percentage of real users are setting up ethernet vs
>     > wifi on them. (anyone?)
>
> Ethernet is not dead for the reasons that wifi is bloated.
> I know when my neighbours are watching their wifi "FIBE TV", because my
> wifi
> tends to die.  (I think they do 802.11g without backoff to 802.11b)
> *My* "TV" (Wii, OUYA) are on wires for this reason.
>
> I consider jamming their AP... I suspect that apartment dwellers will begin
> to learn to use the wire.
>
>     > What I sort of hope for is that your TV could become part of the
>     > routing infrastructure in the house - *wired* - so you could attach
>     > more devices to it that wouldn't need their own connections...
>
> I agree, it would be nice: the TV is big enough to put a pretty decent
> antenna inside, and it's in the place where the people and devices are.
>
> I personally didn't understand why TiVo didn't buy Skype ten years ago.
> TiVo
> had simultaneous MP4 encode and decode and network; all it needed was a USB
> camera on top of the TV, and it's a video phone.
>
> --
> ]               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    [
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

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

  reply	other threads:[~2016-04-18 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 14:50 Dave Taht
2016-04-18 16:08 ` Michael Richardson
2016-04-18 16:14   ` Luis E. Garcia [this message]
2016-04-18 16:32     ` Dave Taht
2016-04-18 16:35 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2016-04-18 18:03   ` Aaron Wood
2016-04-18 23:10 ` [Cerowrt-devel] " Dave Taht
2016-04-19 17:51   ` 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='CALnBQ5=X8+1nvggYbY-cpTrQq8e5UGCfANPsw+ycFq0Yh2=mXg@mail.gmail.com' \
    --to=luis@bitamins.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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