From: Simon Barber <simon@superduper.net>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Michael Yartys <michael.yartys@protonmail.com>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Bufferbloat on Norwegian train wifi
Date: Mon, 22 Jun 2020 13:29:19 -0700 [thread overview]
Message-ID: <A81112B8-1CA0-41BE-8664-3FD590F8F479@superduper.net> (raw)
In-Reply-To: <87tuz3tgaq.fsf@toke.dk>
My record was on a Gogo inflight inernet connection. Ping time of 12 minutes!!!! Perhaps I should have complained that I only got 48 minutes out of my 1 hour session?
Simon
> On Jun 22, 2020, at 5:51 AM, Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
>> I've always noticed that the wireless network on Norwegian Vy trains
>> around Oslo can be close to useless with page load time in excess of
>> 10 seconds and frequent timeouts. That's why I decided to bring along
>> the laptop to run an RRUL BE test, and the results are, as expected,
>> pretty terrible. Mind you, I ran this test while the train was in a
>> tunnel, but I don't think that should matter all that much since
>> there's good 4G service in the tunnel.
>>
>> I've attached the flent data file. Average ping is around 800 ms at
>> the highest, while ICMP spikes above 1000 ms at the highest. I get
>> well below 1 Mbps of download bandwidth, and the upload bandwidth is
>> considerably higher but quite variable at 3 to 15 Mbps.
>
> Yeah, that seems pretty bad. Although my personal record for bloat on a
> train was around ~30 seconds ;)
>
> Guess you could try complaining to the operator, but it may be difficult
> to get hold of anyone with enough of a clue to actually do something
> about this. And since the service is likely to be oursourced, you'll
> need to get the train operator to apply pressure to the company
> providing the service to get them to care. Tried to get Icomera (the
> company providing the internet in Swedish and German trains, among
> others) to care about bufferbloat some years back; but was totally
> unsuccessful :/
>
> -Toke
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
next prev parent reply other threads:[~2020-06-22 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.607.1592728703.24343.make-wifi-fast@lists.bufferbloat.net>
2020-06-22 12:51 ` Toke Høiland-Jørgensen
2020-06-22 20:29 ` Simon Barber [this message]
2020-06-22 21:14 ` Michael Yartys
2020-06-23 10:11 ` Toke Høiland-Jørgensen
2020-06-24 8:56 ` Michael Yartys
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A81112B8-1CA0-41BE-8664-3FD590F8F479@superduper.net \
--to=simon@superduper.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=michael.yartys@protonmail.com \
--cc=toke@redhat.com \
/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