From: J Pan <Pan@uvic.ca>
To: David Lang <david@lang.hm>
Cc: Dave Taht <dave.taht@gmail.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink and VPN
Date: Thu, 23 Jan 2025 09:31:51 -0800 [thread overview]
Message-ID: <CAHn=e4gQSr1iLNo9w6f2PaVDpOpssLqLemMhBQuRMOCr5sfJfw@mail.gmail.com> (raw)
In-Reply-To: <r37p9415-11qq-o52q-npqs-9s13qn2s503r@ynat.uz>
http://tailscale.com works well on starlink (zero configuration
powered by wireguard ;-)
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
On Wed, Jan 22, 2025 at 7:11 PM David Lang via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> Dave Taht wrote:
>
> > How about openvpn over ipv6?
>
> I don't have IPv6 at my house that it's connecting to.
>
> > Or with a static ip assigned to the starlink?
>
> that costs more (and much more than the 50g/m starlink mini plan)
>
> David Lang
>
> > Wireguard works for me....
> >
> > On Tue, Jan 21, 2025 at 3:02 PM Dino Farinacci via Starlink
> > <starlink@lists.bufferbloat.net> wrote:
> >>
> >> I haven't tried openvpn but I have done a bunch of testing of LISP over Starlink. If anyone wants details I can point you to an Internet Draft and slides that have been presented a couple of times at IETF.
> >>
> >> Dino
> >>
> >>> On Jan 20, 2025, at 11:25 PM, 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
> >
> >
> >
> >_______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
prev parent reply other threads:[~2025-01-23 17:32 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
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 [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='CAHn=e4gQSr1iLNo9w6f2PaVDpOpssLqLemMhBQuRMOCr5sfJfw@mail.gmail.com' \
--to=pan@uvic.ca \
--cc=dave.taht@gmail.com \
--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