From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] the network is devolving
Date: Mon, 4 Sep 2023 07:47:24 -0700 [thread overview]
Message-ID: <CALQXh-MWTW8bzAx-9e=LSgyNo6=3sWLSQqG9=2=Uw6Gj_r5QLQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw44mmW3_0_iWwbF2jw2rLU+o+RTWMuEkj6pgE5GadResw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
10Mbit single pair would be for an entirely different application than the
printer, though. That’s a single-pair power-and-data solution for a
microcontroller/sensor network. 1km is good for that speed off of a single
twisted pair. In my past experience that would have been 40-100kbps at
most (industrial automation networks)
-Aaron
- Sent from my iPhone.
On Fri, Sep 1, 2023 at 4:42 PM Dave Taht via Cerowrt-devel <
cerowrt-devel@lists.bufferbloat.net> wrote:
> I see 100Mbit printers... and now 10Mbit single pair for 1km distance
> is becoming a thing
>
> https://electricui.com/blog/spe-sensor-node
>
> --
> Oct 30:
> https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
> Dave Täht CSO, LibreQos
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 1891 bytes --]
prev parent reply other threads:[~2023-09-04 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 23:42 Dave Taht
2023-09-04 14:47 ` Aaron Wood [this message]
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='CALQXh-MWTW8bzAx-9e=LSgyNo6=3sWLSQqG9=2=Uw6Gj_r5QLQ@mail.gmail.com' \
--to=woody77@gmail.com \
--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