Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Gert Doering <gert@space.net>
To: David Lang <david@lang.hm>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink and VPN
Date: Tue, 21 Jan 2025 16:36:30 +0100	[thread overview]
Message-ID: <Z4--_slOenLdVuJF@Space.Net> (raw)
In-Reply-To: <269839o2-003o-1756-8r28-3on7q7nsrn54@ynat.uz>

Hi,

On Mon, Jan 20, 2025 at 11:25:04PM -0800, David Lang via Starlink wrote:
> 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

If the VPN comes up (both sides declare TLS handshake success, you see
the PUSH_REPLY messages on both sides), with TCP, it "should just work"
- if not, it's not a starlink issue but something in the OpenVPN setup,
or just a plain "ipv4_forward=1" missing on the server side...

Feel free to unicast me your OpenVPN logs (verb 3) if needed.

With UDP, "it should also work just fine", but MTU might interfere - and
of course UDP rate limiting.  Try "openvpn --max-packet-size 1000" or 
even lower, if it's really MTU related (tcpdump on both ends on the outside
interface should show if packets are getting lost).

Gert Doering
        -- openvpn upstream
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Ingo Lalla,
                                           Karin Schuler, Sebastian Cler
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

  parent reply	other threads:[~2025-01-21 15:36 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
2025-01-21 16:14     ` Keith Simonsen
2025-01-21 16:45       ` David Lang
2025-01-21 15:36 ` Gert Doering [this message]
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=Z4--_slOenLdVuJF@Space.Net \
    --to=gert@space.net \
    --cc=david@lang.hm \
    --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