Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink and VPN
Date: Tue, 21 Jan 2025 06:43:03 -0500	[thread overview]
Message-ID: <67b7dbb1-d9d9-4127-89c8-92a32fefbf0d@rogers.com> (raw)
In-Reply-To: <269839o2-003o-1756-8r28-3on7q7nsrn54@ynat.uz>

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

Not with openvpn, but there are discussions of using tailscale instead.  
A reddit thread is at

www.reddit.com

Reddit - Dive into anything <#>

🔗 
https://www.reddit.com/r/Tailscale/comments/1ekymc1/use_tailscale_with_starlink_internet/ 
<https://www.reddit.com/r/Tailscale/comments/1ekymc1/use_tailscale_with_starlink_internet/> 


  --dave

On 1/21/25 02:25, David Lang via Starlink wrote:
> has anyone done any work with openvpn over starlink (especially if 
> they got the connectors to completely bypass the router)?
>
> I've got the basic connectivity working, but am having problems trying 
> to get openvpn to work (especially for traffic back through the cgnat 
> to the router on the starlink side)
>
> the logs on the client are reporting link local: (not bound) when 
> trying UDP, when I try TCP (and clamp the mtu low) I can connect from 
> the starlink side (st least sometimes) but cannot get the routing the 
> other way to work
>
> David Lang
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |              -- Mark Twain

[-- Attachment #2: Type: text/html, Size: 3064 bytes --]

  reply	other threads:[~2025-01-21 11:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21  7:25 David Lang
2025-01-21 11:43 ` David Collier-Brown [this message]
2025-01-21 15:12 ` b. angel
2025-01-21 15:22   ` David Lang
2025-01-21 15:27     ` Sebastian Moeller
2025-01-21 15:36       ` Nils Andreas Svee
2025-01-21 15:45       ` David Lang
2025-01-21 16:14     ` Keith Simonsen
2025-01-21 16:45       ` David Lang
2025-01-21 15:36 ` Gert Doering
2025-01-21 15:52   ` David Lang
2025-01-21 23:02 ` Dino Farinacci
2025-01-22 22:53   ` Dave Taht
2025-01-22 23:25     ` Dino Farinacci
2025-01-22 23:29       ` Darrell Budic
2025-01-22 23:42         ` Dino Farinacci
2025-01-23  3:10     ` David Lang
2025-01-23 17:31       ` J Pan

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=67b7dbb1-d9d9-4127-89c8-92a32fefbf0d@rogers.com \
    --to=davec-b@rogers.com \
    --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