From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4090C3B29E; Fri, 26 Feb 2021 09:25:31 -0500 (EST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 16A1CB57; Fri, 26 Feb 2021 09:25:30 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 26 Feb 2021 09:25:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lochnair.net; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm2; bh=odxkQW3PBKT+yw7g9YBjlfCyVY+ dS2ynxR13ZHS049s=; b=IJs1uJV7wpVf6nCtkSeREJ5GfvB7tS8CMNe2PeLcU/L 7oue1Si3kBbGrBQe7XxCS8/Ucy4ki398f6evJZAnL8utIpHPoLjEuFtE2ef+F4DX 7h6ecCJvzeJLuzTAkAf74sQud0cC0xFvnZwaXuAei5hBfw5Iv5ImJXvPNgiHWBz1 HPPJe46ThTL51yPOIIO7z/ia3lgt9UHqgBjQGKnp8f3T2XTvEMXfQDADfFuV2nWp 0j6CPZi3kCMZ06chMRitatVdh16xSAJEX8VSedW6hQirF7smEu+4dRewbXkpFmNe zdktT+wxCFmmWvcvysUPGQqbreanXdtJKd64YU895FQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=odxkQW 3PBKT+yw7g9YBjlfCyVY+dS2ynxR13ZHS049s=; b=RD6mhQtC8TwjuHvwfc5m97 wTu6jdlLjJnen2eeEu8OMQWXa1ZQxCFMQSzDxJNAV7XynMFSXKoq6TIvtKKIAS7H GsRnVM1XrYod9gtklKRj3VpYISq6W6egzMiWIg7itmtIdFkJd6dC0WPxDbBAGO3Z W2uexj7SiKv4XmMtSW6juaZklIWl2+89Kjr2hNYpnAGB0uWOLuvtAtu/4HyG3z3s I7xOqiqW60iTP2zZmBcIeMKLhUItzQD//pIDjK6jAoOOKl1a0rr+XR15ZWyXhiVh YzTpqtJ/16Hw7/1YAhSbR0pRdyj27r+1TGyAYv17rjyXNnKOuKkZ/MhreuValzJw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrledugdeiiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgesrgdtreertdefheenucfhrhhomheppfhilhhsucet nhgurhgvrghsucfuvhgvvgcuoehmvgeslhhotghhnhgrihhrrdhnvghtqeenucggtffrrg htthgvrhhnpeeigeeiffegheegteejgfdtieevkedvuefhtdefhfdvvdfhieegueevffek jefgjeenucfkphepjeejrddukedrudegkedruddtgeenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmvgeslhhotghhnhgrihhrrdhnvght X-ME-Proxy: Received: from [10.1.100.229] (77.18.148.104.tmi.telenormobil.no [77.18.148.104]) by mail.messagingengine.com (Postfix) with ESMTPA id 6439624005D; Fri, 26 Feb 2021 09:25:28 -0500 (EST) To: Taraldsen Erik , Dave Taht , bloat , Make-Wifi-fast , =?UTF-8?Q?Toke_H=c3=b8iland-J=c3=b8rgensen_via_Cake?= References: <874ki24ref.wl-jch@irif.fr> <1e41ddf7-cd08-4fec-b31a-3021f8111dc6@www.fastmail.com> <2f30c201fce345658df9f2a5090745cf@telenor.no> <480413c4-e9a1-4b78-8ef6-3d8658836874@www.fastmail.com> <9b17aa66-d02d-e262-88a3-2f36c1755667@lochnair.net> <53f6b6b3f5b043feb841c9c33fd1f480@telenor.no> From: Nils Andreas Svee Message-ID: <26ed70a5-6638-3298-3c8a-467b2561dbbf@lochnair.net> Date: Fri, 26 Feb 2021 15:25:25 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: <53f6b6b3f5b043feb841c9c33fd1f480@telenor.no> Content-Type: multipart/alternative; boundary="------------AED6AECBA902565A2E4E83B6" Content-Language: en-US Subject: Re: [Cake] [Bloat] Fwd: [Galene] Dave on bufferbloat and jitter at 8pm CET Tuesday 23 X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2021 14:25:31 -0000 This is a multi-part message in MIME format. --------------AED6AECBA902565A2E4E83B6 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit On 2/26/21 8:26 AM, Taraldsen Erik wrote: > *Fra:* Nils Andreas Svee > > I am indeed running them on Ethernet. I don't actually use the > B818 for anything else than as a LTE modem, so I wouldn't know, if > I could get the thing to bridge I would. Or replace it with > something else entirely that I can control, but that doesn't seem > to be an option on FWA. That said the Zyxel looks like a better > option since I assume it acts like a bridge by default. > > The Zyxel device indeed acts as a bridge, or at least as close > approximation as we can get it.  The PDP addressing protocol in mobile > networks requres the address termination to happen where the SIM card > resides.  So the device does some trickery with brctl, routing and > iptables to simulate a bridge setup. > Oh nice. Sure it's not a "true" bridge, but for all intents and purposes it gets the job done. Kinda tempting to get one of those now, if only to avoid the whole using DMZ mode on the B818 to pass everything through. > > I dumped the raw signal stats the web interface grabs in an XML > file together with the Flent tests. Also did some upload only > tests tonight at different speeds (no VPN in play this time). > > rsrp is good and rsrq is great at your location.  However you have > ended up on the 800MHz band.  That is intended for coverage, not > capacity.  It uses only 10MHz bandwitdh and is shared with a lot more > customers.  You probably should be able to get an 1800MHz frequency > which has 20MHz and is shared among fewer customers. > Yeah I thought it should be pretty good. I don't really know how to interpret those numbers, but Teltonika's guidelines seemed to indicate that it should be good. Good point about the bands. For the first months after we signed up it tended to switch between 800Mhz and 1800Mhz and mostly stay on 1800Mhz, but now it's been stuck on 800Mhz for quite some time. I wanted to try and lock it to 1800Mhz, but there's no option for that exposed in the GUI that I can find. > Most likely yes. That's been my observation as well, that it > generally acts up the worst when somethings using the upstream. > Not entirely sure what I can do about that, seeing as I had to > shape at 5Mbit to get rid of the worst spikes (but not all). > > This is tricky.  You don't have a static set of resources.  You > request resources "as needed".  The "as needed" amongst other things > reads the buffer back pressure.  So if you shape to far down the LTE > device will not request enough resources.  Shape to high and there > will not be enough resources available to share.  And available > resources vary with number of subscribers on that cell, weather, the > subscribers usage and interference from other cell towers.  To get a > proper solution to this I don't see a way around getting the chipset > manufacturers on board. > > Downside of shared mediums of course. So basically my best bet is to find somewhere in the middle to shape on, or use the pping stuff to somehow dynamically configure it. Of course, but we don't really have a voice with them, so the best we can do is support your efforts however we can. > > > On that point, I would've liked to collect signal stats over time, > but the B818 seems to insist on chucking me out after being idle > for a few minutes, better known as scraping the stats with cURL > > > Have you tried to use the telnet service port (20249) on the B818?  > Not all variants have that open but you could give it a shot.  You > also may need to acquire an datalock code for the "at^datalock=" command. > > telnet LAN_IP 20249 > I had not, I didn't scan higher ports. It *is* open though, so I was able to connect to it. It only yells at me if I try to run any of the few AT commands I know (except /at)/, not sure if that's because of the datalock code. If that's what I'm missing, how does one go about getting a hold of one of those? When I looked it up I only found some sites I have concern about the legitimacy of. > > > This is getting LTE/5G spesific.  Not sure if it belongs on the list.  > Let us know if we are generating noise. > > > -Erik --------------AED6AECBA902565A2E4E83B6 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit


On 2/26/21 8:26 AM, Taraldsen Erik wrote:
Fra: Nils Andreas Svee <me@lochnair.net>

I am indeed running them on Ethernet. I don't actually use the B818 for anything else than as a LTE modem, so I wouldn't know, if I could get the thing to bridge I would. Or replace it with something else entirely that I can control, but that doesn't seem to be an option on FWA. That said the Zyxel looks like a better option since I assume it acts like a bridge by default.
The Zyxel device indeed acts as a bridge, or at least as close approximation as we can get it.  The PDP addressing protocol in mobile networks requres the address termination to happen where the SIM card resides.  So the device does some trickery with brctl, routing and iptables to simulate a bridge setup.

Oh nice. Sure it's not a "true" bridge, but for all intents and purposes it gets the job done. Kinda tempting to get one of those now, if only to avoid the whole using DMZ mode on the B818 to pass everything through.

I dumped the raw signal stats the web interface grabs in an XML file together with the Flent tests. Also did some upload only tests tonight at different speeds (no VPN in play this time).
rsrp is good and rsrq is great at your location.  However you have ended up on the 800MHz band.  That is intended for coverage, not capacity.  It uses only 10MHz bandwitdh and is shared with a lot more customers.  You probably should be able to get an 1800MHz frequency which has 20MHz and is shared among fewer customers.

Yeah I thought it should be pretty good. I don't really know how to interpret those numbers, but Teltonika's guidelines seemed to indicate that it should be good.

Good point about the bands. For the first months after we signed up it tended to switch between 800Mhz and 1800Mhz and mostly stay on 1800Mhz, but now it's been stuck on 800Mhz for quite some time.

I wanted to try and lock it to 1800Mhz, but there's no option for that exposed in the GUI that I can find.

Most likely yes. That's been my observation as well, that it generally acts up the worst when somethings using the upstream. Not entirely sure what I can do about that, seeing as I had to shape at 5Mbit to get rid of the worst spikes (but not all).

This is tricky.  You don't have a static set of resources.  You request resources "as needed".  The "as needed" amongst other things reads the buffer back pressure.  So if you shape to far down the LTE device will not request enough resources.  Shape to high and there will not be enough resources available to share.  And available resources vary with number of subscribers on that cell, weather, the subscribers usage and interference from other cell towers.  To get a proper solution to this I don't see a way around getting the chipset manufacturers on board.


Downside of shared mediums of course. So basically my best bet is to find somewhere in the middle to shape on, or use the pping stuff to somehow dynamically configure it. Of course, but we don't really have a voice with them, so the best we can do is support your efforts however we can.


On that point, I would've liked to collect signal stats over time, but the B818 seems to insist on chucking me out after being idle for a few minutes, better known as scraping the stats with cURL


Have you tried to use the telnet service port (20249) on the B818?  Not all variants have that open but you could give it a shot.  You also may need to acquire an datalock code for the "at^datalock=" command.  

telnet LAN_IP 20249

I had not, I didn't scan higher ports. It *is* open though, so I was able to connect to it. It only yells at me if I try to run any of the few AT commands I know (except at), not sure if that's because of the datalock code. If that's what I'm missing, how does one go about getting a hold of one of those? When I looked it up I only found some sites I have concern about the legitimacy of.


This is getting LTE/5G spesific.  Not sure if it belongs on the list.  Let us know if we are generating noise.


-Erik
--------------AED6AECBA902565A2E4E83B6--