Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: David Reed <dpreed@reed.com>
Cc: "Wes Felter" <wmf@felter.org>,
	"Joel Wirāmu Pauling" <joel@aenertia.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 10GigE nics and SFP+ modules?
Date: Thu, 11 Sep 2014 08:30:52 -0700	[thread overview]
Message-ID: <CAA93jw7Njvui94tUWWuW_s=HUgj4JQtEhQQiY-v+HROknA_mNw@mail.gmail.com> (raw)
In-Reply-To: <1410377469.392315248@apps.rackspace.com>

On Wed, Sep 10, 2014 at 12:31 PM,  <dpreed@reed.com> wrote:
> I'm confused....
>
>
>
> SFP is not SFP+.   SFP carries at most 4.25 Gb/sec.   SFP+ works at >10
> Gb/sec.   So, it's not clear that the MikroTik is very useful in a 10 Gig
> world.  It's not immediately clear but VERY likely, that this is an "edge
> switch" that is intended for collapsing the GigE copper traffic onto a
> potentially bottlenecked GigE "local backbone".

Yes. And as such it's the cheapest I've ever seen. You can find slightly larger,
rack mount SFP capable switches, but nothing in this form factor that I know
of exists.

> Of course if you want to go from GigE fiber to GigE copper, that board might
> be useful.

In my case, I ended up trying to figure out what the costs would be
for 1G FTTY, which is a run of about 200 meters. This could be a
welcome change from the current 6 hop wifi mesh network in place to
get to the internet from where I sit. As fond as I am of wifi, even
with having high hopes to improve it further, sometimes a cable is
just better.

This was a wonderfully wide-ranging conversation overall, along the
way I learned about the differences between SFP, SFP+, and GSFTP, how
to crimp and run cables, and many of the relevant costs involved at
every layer in doing it...

thank you all for sharing your knowledge!

In my life I've punched holes in coax, run arcnet, climbed mountains
and tall buildings to run wifi P2P links and cut and crimped more
twisted pair than I care to remember, but my exposure to fiber's
methods has been sadly limited, til now.

I still don't quite have a grip on how and when to use various forms
of cwdm or what wavelengths make the most sense, when...



-- 
Dave Täht

https://www.bufferbloat.net/projects/make-wifi-fast

  reply	other threads:[~2014-09-11 15:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 18:05 Dave Taht
2014-09-10 18:09 ` Nicholas Weaver
2014-09-10 19:31 ` dpreed
2014-09-11 15:30   ` Dave Taht [this message]
2014-09-13  2:48     ` Chuck Anderson
2014-09-10 20:03 ` Michael Richardson
2014-09-10 21:54   ` Joel Wirāmu Pauling
  -- strict thread matches above, loose matches on Subject: below --
2014-09-06 18:36 Dave Taht
2014-09-06 19:05 ` dpreed
2014-09-06 20:44   ` Dave Taht
2014-09-09  0:09 ` Wes Felter
2014-09-09  4:03   ` Joel Wirāmu Pauling
2014-09-09  4:06     ` Joel Wirāmu Pauling
2014-09-09 16:26       ` dpreed
2014-09-09 16:54         ` Dave Taht
2014-09-10  7:01           ` Mikael Abrahamsson
2014-09-09 19:06       ` Wes Felter
2014-09-10  1:14         ` Dave Taht
2014-09-10  6:43     ` Mikael Abrahamsson

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='CAA93jw7Njvui94tUWWuW_s=HUgj4JQtEhQQiY-v+HROknA_mNw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    --cc=joel@aenertia.net \
    --cc=wmf@felter.org \
    /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