Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Adam Thompson <athompson@merlin.mb.ca>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] VPN woes, recommendations?
Date: Fri, 17 Feb 2023 13:01:18 -0800 (PST)	[thread overview]
Message-ID: <53ssr050-3n7s-4647-22p7-1428r6646oo6@ynat.uz> (raw)
In-Reply-To: <YQBPR0101MB89254CCAC6EB4DB67D5BD6C59BA19@YQBPR0101MB8925.CANPRD01.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

On Fri, 17 Feb 2023, Adam Thompson via Starlink wrote:

> First, having multiple devices in serial is generally not a great idea for reliability.  Can we realistically plug our remote AP directly into the dish, still?  (This is using Starlink Business, FWIW.). I know we lose access to the Starlink app, but we also lose a NATing router and an unwanted wifi AP, so that's probably a net zero.  I just don't know what other dangers/problems that topology might cause.

look at youtube for people running their starlink on 12v, it requires cutting 
the cable and putting normal ends on it, but once you do that (and have a PoE 
power injector) you can connect a normal router to a starlink dish

I haven't heard of anyone doing this for the larger dish, but for the standard 
one it's quite common.

The dish then gives you a 192.168.1 IP address (and only one, so you still have 
your router NAT and dish NAT involved)

David Lang

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink

      parent reply	other threads:[~2023-02-17 21:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 16:30 Adam Thompson
2023-02-17 16:34 ` Dave Taht
2023-02-17 16:36 ` Daniel C. Eckert
2023-02-17 16:38   ` Adam Thompson
2023-02-17 16:39   ` Adam Thompson
2023-02-17 16:45     ` Dave Taht
2023-02-17 17:38       ` Adam Thompson
2023-02-17 17:40         ` Dave Taht
2023-02-17 16:47     ` Nathan Owens
2023-02-17 18:29 ` Michael Richardson
2023-02-17 21:01 ` David Lang [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/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=53ssr050-3n7s-4647-22p7-1428r6646oo6@ynat.uz \
    --to=david@lang.hm \
    --cc=athompson@merlin.mb.ca \
    --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