From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F3A2D3B2A4 for ; Mon, 22 Jun 2020 08:51:15 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592830275; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=G8vlLGhY2M1rjEIeK6XLlDTW/80PqQvxIrq/1NGYCv4=; b=f2yiWkR46osX5eCfaRXc5fIfvfNorH2tLeevcu3QhsRWdlycgxB18uZAI8pwrPCcECYZhL Cl8ivnTutknKIOv+qlMRVyWKbH/nFgcdMqyTAl1Nd3CJkkz/GbNssj4SSkvhZY13x6VPIy rP38U8/9CNH/XmIZJEpEpChxeKfgmk4= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-78-HfkH74usOdafYLqCWZr8gQ-1; Mon, 22 Jun 2020 08:51:13 -0400 X-MC-Unique: HfkH74usOdafYLqCWZr8gQ-1 Received: by mail-wr1-f72.google.com with SMTP id w4so10819311wrl.13 for ; Mon, 22 Jun 2020 05:51:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=G8vlLGhY2M1rjEIeK6XLlDTW/80PqQvxIrq/1NGYCv4=; b=DfgcUWjV+2icE7PHojUe58Fbb/Y4h4WYY41PS+7FYXjgFlmWRLbOXlS+EW8qJ8HVai GfecLkM/dWWlvN1S2iFYeSia49FIAHQ5DLxlzYGL1Xs0uMmiz4Q6Ag2rdlZqtfaDGt/c V8U+Tw2VKe8OW3t95eIYEJW2ETQQKTh694DAnzfdDjmjbT0HhIefsQB2uJkfD2I7AuLJ T4n2IPJXkmCbMUCbxVLg84BrRhrnXbmz6lQm6KVZ+jXToALw7lPC3zCYywjt/IRbKSGT ISYzt4XdHQ222whSokQIK/L4s++C7tzgrD6Hv0EtsZNawXP+HiKMzSp4biNb3DKpg3aq TcmA== X-Gm-Message-State: AOAM533Kw+EjdN0K5Jd/LhdVPGtLEBisRtvmogjHsUxUsTZGb9SUMOU3 iX7Fmuy5Q2tCawE29dzulMnMlTYoM9pga31qH/jxLmVsCeU39hxUtjA6Ylj4kQ6H96NkrplvGut 4+sp/9ndC24iSlo0AKHMBxtSmIea/XmYmU3E= X-Received: by 2002:a7b:cd07:: with SMTP id f7mr6987362wmj.115.1592830271934; Mon, 22 Jun 2020 05:51:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwUI0Z7Bki3BnC080MS/UVED4PH5of4ajC/0YIGgei3G0rZxly4FwGtbNXu090I3ji/DpwURg== X-Received: by 2002:a7b:cd07:: with SMTP id f7mr6987346wmj.115.1592830271758; Mon, 22 Jun 2020 05:51:11 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([45.145.92.2]) by smtp.gmail.com with ESMTPSA id k206sm17173359wma.39.2020.06.22.05.51.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 Jun 2020 05:51:11 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id B5D0A1814F6; Mon, 22 Jun 2020 14:51:09 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Michael Yartys , make-wifi-fast@lists.bufferbloat.net In-Reply-To: References: X-Clacks-Overhead: GNU Terry Pratchett Date: Mon, 22 Jun 2020 14:51:09 +0200 Message-ID: <87tuz3tgaq.fsf@toke.dk> MIME-Version: 1.0 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=toke@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: Re: [Make-wifi-fast] Bufferbloat on Norwegian train wifi X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2020 12:51:16 -0000 > 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