From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Fiber to the yurt approved
Date: Thu, 25 Sep 2014 18:12:58 +1200 [thread overview]
Message-ID: <CAKiAkGSaoVgiTGZOykZ29Bja+=htuO3EDq7nMJm9mSbjL8XPSg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4e_mDT-tZmcK5SbEaMz-MSo2b-mN3u_AZak91BXKx7gQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2284 bytes --]
Put as many pairs as you can fit into the conduit to leave quite a lot of
slack (2-5metres)
We bury our splitters with ofdm break outs in waterproof boxes every 500m -
2km or so for the GPON roll out and blow the Fibre to the premise from the
split. Burying splinter boxes prevents vandalism/flooding issues and
accidents. Con's you have to dig it up every time you want to connect
another pair into the ofdm. Fibre blower kit is expensive.
Choose your connectors on the ofdm carefully. LC style connectors are the
norm on SFP(+) optics and isn't angled. This is my personal favorite but
some dislike it. Is rarely the norm for In premise kit especially for pon.
Angled and unangled SC connectors are norm for PON and CPE Home kit. Angled
is better for loss and used primarily on the splitter OFDM but easy to
munge if you connect angled to unangled.
You might even consider just not using a splinter or OFDM patch at all and
just having slack and unterminated fibers. Cheap Chinese Fujikura
equivalent spilcers can be had for around 3000$ now. And splicing is always
better than patching IME.
Have fun!
-Joel
On 25 Sep 2014 17:11, "Dave Taht" <dave.taht@gmail.com> wrote:
> I just (surprisingly) got approval to do FTTY (fiber to the yurt)
> here. (There are some geeks on the board of directors)
>
> Questions on trenching - got all the equipment (backhoe, etc), but not sure
> what to lay in the ground, how deep, what regs apply, etc.
>
> It sounds like laying conduit is the best option? Sources? 1000 meter
> roll of what? what tools needed? (will look over the various
> tutorials)
>
> The other piece I'm vague on is how to split out each fiber from the
> bundle to each location.
>
> It seems sanest to standardize on single mode fiber (longest run would
> be 600m), would be nice to find an openwrt capable router instead of a
> media converter...
>
>
> http://www.amazon.com/gp/product/B003AVRLZI/ref=s9_simh_se_p147_d0_i4?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=search-desktop-advertising-no-results-center-1&pf_rd_r=11AB4X7H6AZMPAKH0WSG&pf_rd_t=301&pf_rd_p=1912906182&pf_rd_i=fiber%20ground%20burial
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 3167 bytes --]
next prev parent reply other threads:[~2014-09-25 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 5:11 Dave Taht
2014-09-25 6:12 ` Joel Wirāmu Pauling [this message]
2014-09-25 14:06 ` Dave Taht
2014-09-25 14:53 ` Chuck Anderson
2014-09-30 22:49 ` 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='CAKiAkGSaoVgiTGZOykZ29Bja+=htuO3EDq7nMJm9mSbjL8XPSg@mail.gmail.com' \
--to=joel@aenertia.net \
--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