Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: David Lang <david@lang.hm>, "b. angel" <blakangel@gmail.com>,
	 Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] starlink and VPN
Date: Tue, 21 Jan 2025 07:45:31 -0800 (PST)	[thread overview]
Message-ID: <s19n7196-5os2-n7ns-5ro7-047q2sos7367@ynat.uz> (raw)
In-Reply-To: <D748D4E8-5872-4A32-81DE-4EE15E21EB2A@gmx.de>

Sebastian Moeller wrote:

> Hi David,
>
>> On 21. Jan 2025, at 16:22, David Lang via Starlink <starlink@lists.bufferbloat.net> wrote:
>>
>> b. angel wrote:
>>
>>> David,
>>>
>>> I gave up on open VPN and starlink a while ago. I've implemented wireguard
>>> tunnels with success and reliability.
>>
>> did you end up having to do anything with MTU? Did you use TCP or UDP for your transport?
>
> Wireguard itself only allows UDP IIRC, you would need an additional outer TCP tunnel if you want/need TCP on the outside...

I agree UDP is preferred, I'm just trying to figure out what has successfully 
worked. In my google searches yesterday I saw posts from Starlink saying that 
they don't block VPNs (but won't help troubleshoot) and a lot of people saying 
that they didn't work

David Lang


>>
>> David Lang
>>
>>> Keith
>>>
>>> On Mon, Jan 20, 2025, 23:25 David Lang via Starlink <
>>> starlink@lists.bufferbloat.net> 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
>>>>
>>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>
>

  parent reply	other threads:[~2025-01-21 15:45 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
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 [this message]
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=s19n7196-5os2-n7ns-5ro7-047q2sos7367@ynat.uz \
    --to=david@lang.hm \
    --cc=blakangel@gmail.com \
    --cc=moeller0@gmx.de \
    --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