From: Inemesit Affia <inemesitaffia@gmail.com>
To: Jim Forster <jim@connectivitycap.com>
Cc: Starlink <Starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Question on Startlink density
Date: Wed, 15 Nov 2023 07:55:25 +0100 [thread overview]
Message-ID: <CAJEhh73Jv29wPNtqG6BmuKT_PA6Gg9iaOspJa=0FmRC0_-zP7w@mail.gmail.com> (raw)
In-Reply-To: <34D160E7-6C8F-4882-B1C3-570DF3D3854F@connectivitycap.com>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
What you're planning might we'll be against the Starlink TOS.
Just contact https://old.reddit.com/user/millijuna. He's done something
similar
Beyond that networks are networks. You estimate your peak traffic, find out
the worst case speed on starlink and get software/hardware to shape &
prioritize traffic/users so phone calls work when the WAN can't do video.
Check out libreqos
Also the owner of starlink.sx is on this mailing list and has experience
with this sort of thing
On Wed, Nov 15, 2023, 7:13 AM Jim Forster via Starlink <
starlink@lists.bufferbloat.net> wrote:
>
> Does Starlink’s beam forming support delivering services to about 100 home
> stretched over one mile? The place in question would like to do fiber, but
> it’s in a senstive area, so getting permits is tricky (cannot use any
> previously undisturbed land), and so the fiber project has dragged on. Now
> SL is available and some are getting it. That’s fine, but could it support
> 100 over one linear mile?
>
> Thanks,
>
> — Jim
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 1919 bytes --]
next prev parent reply other threads:[~2023-11-15 6:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 21:01 [Starlink] run a few scripts behind your starlink dish? J Pan
2023-11-15 6:12 ` [Starlink] Question on Startlink density Jim Forster
2023-11-15 6:55 ` Inemesit Affia [this message]
2023-11-15 6:56 ` Inemesit Affia
2023-11-15 7:01 ` Jim Forster
2023-11-15 7:04 ` David Lang
2023-11-15 7:07 ` J Pan
2023-11-15 8:05 ` Jim Forster
2023-11-15 14:38 ` J Pan
2023-11-15 7:03 ` David Lang
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJEhh73Jv29wPNtqG6BmuKT_PA6Gg9iaOspJa=0FmRC0_-zP7w@mail.gmail.com' \
--to=inemesitaffia@gmail.com \
--cc=Starlink@lists.bufferbloat.net \
--cc=jim@connectivitycap.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