From: J Pan <Pan@uvic.ca>
To: Noel Butler <noel.butler@ausics.net>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Info on IP country ranges
Date: Mon, 4 Dec 2023 10:17:58 -0800 [thread overview]
Message-ID: <CAHn=e4jaLBsPVJ7VcYrpBEeY9V6Jmv5uVSqP2Q2zq386B2OPVw@mail.gmail.com> (raw)
In-Reply-To: <75790520d6c8d35beb7248f5f5dff952@ausics.net>
yes, starlink does respond to its customers' complaints, although
sometimes slowly. its ipv4 address acquisition is scattered around as
a latecomer to the isp world, and as a global local isp, it's more
troublesome. ip packets have to be tunneled back to its home pop where
nat and other functions happen, sometimes around the world, causing a
much higher minimum rtt fluctuation in 15-second handover
intervals---bad for network protocols and applications. ipv6 can do
better but currently follows the same route as ipv4---an incentive to
promote ipv6 ;-)
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
On Mon, Dec 4, 2023 at 4:04 AM Noel Butler <noel.butler@ausics.net> wrote:
>
> Thanks, it seems they are trying it on then :)
>
> On 04/12/2023 10:44, J Pan wrote:
>
> starlink advertises its customer ip address location at
> http://geoip.starlinkisp.net (not always updated but good enough in
> most cases and traceroute can confirm to some extent as well)
> --
> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
>
> On Sun, Dec 3, 2023 at 4:15 PM Noel Butler via Starlink
> <starlink@lists.bufferbloat.net> wrote:
>
>
> I run an open access usenet server, but only for those within my CC, so access is by IP based on our CC allocations from APNIC.
>
> Because IPv4 exhaustion this changes sometimes with buying allocations from other regions, and if they get denied access I encourage them to let us know so we can keep ACL's updated, I've had a request from a starlink user who claims they are here, but traceroute shows them in .DE
>
> tracing some 217.foo.ad.dr
>
> ...
> 9 ae-6.r21.frnkge13.de.bb.gin.ntt.net (129.250.3.183) 290.223 ms 290.180 ms ae-1.r20.frnkge13.de.bb.gin.ntt.net (129.250.7.35) 280.523 ms
> 10 ae-1.a03.frnkge13.de.bb.gin.ntt.net (129.250.3.152) 290.109 ms 289.667 ms 292.864 ms
> 11 ae-0.spacex.frnkge13.de.bb.gin.ntt.net (213.198.72.19) 279.611 ms 278.840 ms 279.592 ms
> 12 undefined.hostname.localhost (206.224.65.189) 280.127 ms 278.506 ms 284.265 ms
> 13 undefined.hostname.localhost (206.224.65.209) 284.198 ms undefined.hostname.localhost (206.224.65.201) 274.663 ms 273.073 ms
> 14 * * *
>
>
> As it is our policy to not collect any user info or issue user/pass's and only allow access by IP, I'm hoping someone here knows if they are full of it, or does starlink really assign addresses from anywhere? That one hardly makes sense for user experience, or maybe starlink has so few users in this country they haven't bothered changing anything yet?
>
> --
>
> Regards,
> Noel Butler
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>
> --
>
> Regards,
> Noel Butler
>
>
next prev parent reply other threads:[~2023-12-04 18:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 0:15 Noel Butler
2023-12-04 0:44 ` J Pan
2023-12-04 12:04 ` Noel Butler
2023-12-04 18:17 ` J Pan [this message]
2023-12-07 11:54 ` Alexandre Petrescu
2023-12-07 18:07 ` J Pan
2023-12-07 20:10 ` Alexandre Petrescu
2023-12-07 20:40 ` David Lang
2023-12-08 5:57 ` Freddie Cash
2023-12-08 8:30 ` Alexandre Petrescu
2023-12-08 8:37 ` Alexandre Petrescu
2023-12-08 15:27 ` Freddie Cash
2023-12-08 17:26 ` Alexandre Petrescu
2023-12-08 8:40 ` Steven
2023-12-08 10:22 ` Alexandre Petrescu
2023-12-08 10:31 ` Steven
2023-12-08 11:48 ` Alexandre Petrescu
2023-12-08 11:54 ` Steven
2023-12-08 12:07 ` Alexandre Petrescu
2023-12-08 12:24 ` Steven
2023-12-08 12:46 ` Alexandre Petrescu
2023-12-08 14:15 ` Alexandre Petrescu
2023-12-11 15:30 ` Alexandre Petrescu
2023-12-12 1:09 ` Steven Honson
2023-12-12 2:29 ` J Pan
2023-12-12 2:43 ` Steven
2023-12-12 10:22 ` Alexandre Petrescu
2023-12-12 10:33 ` Steven
2023-12-12 10:50 ` Sebastian Moeller
2023-12-13 10:33 ` Alexandre Petrescu
2023-12-13 14:37 ` Marc Blanchet
2023-12-13 18:27 ` David Lang
2023-12-14 13:27 ` Alexandre Petrescu
2023-12-23 21:35 ` J Pan
2024-01-06 15:01 ` Alexandre Petrescu
2024-01-08 10:01 ` [Starlink] starlink topology with tunnels (was: Info on IP country ranges) Alexandre Petrescu
2024-01-08 10:06 ` [Starlink] starlink topology with tunnels Alexandre PETRESCU
2023-12-12 10:52 ` [Starlink] Info on IP country ranges Alexandre Petrescu
2023-12-08 10:28 ` Alexandre Petrescu
2023-12-08 10:31 ` Gert Doering
2023-12-13 20:58 David Fernández
2023-12-13 22:57 ` Marc Blanchet
2023-12-13 22:59 ` Marc Blanchet
2023-12-24 1:29 ` Lukasz Bromirski
2024-01-06 14:59 ` Alexandre Petrescu
2024-01-06 15:06 ` Dave Taht
2024-01-08 10:54 ` Sebastian Moeller
2024-01-08 13:16 ` Alexandre Petrescu
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=e4jaLBsPVJ7VcYrpBEeY9V6Jmv5uVSqP2Q2zq386B2OPVw@mail.gmail.com' \
--to=pan@uvic.ca \
--cc=noel.butler@ausics.net \
--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