From: dan <dandenson@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Dave Täht" <dave.taht@gmail.com>,
"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
"David Fernández" <davidfdzp@gmail.com>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] [Starlink] GPON vs Active Fiber Ethernet
Date: Fri, 17 Mar 2023 17:48:43 -0600 [thread overview]
Message-ID: <CAA_JP8XGorMCqBYQ9C=8KB_6Rt0_miuSNfomtrM1V_ik8tvY6g@mail.gmail.com> (raw)
In-Reply-To: <C8626CF0-5439-4E2D-A462-8E9546880122@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]
per copper vs gpon. There are a lot of parts to this but I think it's safe
to say that any *DSL product is inferior to ethernet or gpon so aren't part
of the conversation. We're really talking ethernet vs *GPON here. No
other fiber options are widespread and viable for most. I don't want to
play both sides here so I'm just talking pros on 'ethernet'. not
'copper'... but also copper.
Ethernet lives on copper or fiber.
Copper 'last meter' is cheap, CHEAPER than any fiber product. Copper is
cheaper until you hit 100m and then fiber wins.
Ethernet is near wire speed *routed* on a number of modern and
weather resistant outdoor products.
Backhauling on multi-strand fiber eliminates one primary negative with
copper in that cost over 100m number.
There's likely some wash in having fiber to the home and the cost of
termination and ONUs vs PoE injectors in home pushing up to powered
switches.
Pro for powered switch is that routing option. Dramatically easier (as in,
it's actually possible) to build rings and meshy routed networks on
ethernet allowing for much more backhoe-fade safe networks. While not as
future proof as fiber strands to the door, it's capable of 1G, 2.5G today
and really 10G for the most part though there is a lack of hardware with
those ports so leave that up in the air. XGSPON wins the max per port
speed here, but that same network with active ethernet over fiber backhauls
and copper can EASILY do 100G on the backhaul and 2.5G/port and even go
hybrid with mostly copper last meter and some active fiber off 10,40,100G
ports when profitable.
It's not all roses, but there are real world scenarios where a methodical
buildout of ethernet can be a better choice especially if we're talking
about maximum performance.
I don't want to lean too heavily on mikrotik here, lots of people aren't in
love with them, but they are definitely pushing boundaries here.
https://mikrotik.com/product/crs504_4xq_out
4x100G switch, outdoor grade, supports 4x breakout cables so can do 4x4x25G
or 2x100G feeds + 2x4x25 or 2x4x10G on a Marvell Prestera switch (presents
as individual interfaces). XGSPON can't touch it. Heck, you could do
remote XGSPON with a TIBIT port if you really wanted to, or feed an
Netpower 7R units with 10Gbps each and get reverse PoE to power everything.
[-- Attachment #2: Type: text/html, Size: 2620 bytes --]
prev parent reply other threads:[~2023-03-17 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC=tZ0rRc_32W3oQN2w2KSNh8W=7eBrmz=2zaRgmzHMQW1r2vA@mail.gmail.com>
2023-03-17 17:05 ` [LibreQoS] " Dave Taht
2023-03-17 20:36 ` [LibreQoS] [Starlink] " Sebastian Moeller
2023-03-17 23:48 ` dan [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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA_JP8XGorMCqBYQ9C=8KB_6Rt0_miuSNfomtrM1V_ik8tvY6g@mail.gmail.com' \
--to=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--cc=davidfdzp@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=starlink@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