From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (unknown [66.167.227.145]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 381E73B29D; Mon, 2 Aug 2021 23:06:22 -0400 (EDT) Received: from dlang-laptop (unknown [10.2.0.162]) by mail.lang.hm (Postfix) with ESMTP id CAD44100109; Mon, 2 Aug 2021 20:06:20 -0700 (PDT) Date: Mon, 2 Aug 2021 20:06:20 -0700 (PDT) From: David Lang X-X-Sender: dlang@dlang-laptop To: Bob McMahon cc: David Lang , Luca Muscariello , Cake List , Make-Wifi-fast , Leonard Kleinrock , starlink@lists.bufferbloat.net, codel@lists.bufferbloat.net, cerowrt-devel , bloat , Ben Greear In-Reply-To: Message-ID: References: <1625188609.32718319@apps.rackspace.com> <989de0c1-e06c-cda9-ebe6-1f33df8a4c24@candelatech.com> <1625773080.94974089@apps.rackspace.com> User-Agent: Alpine 2.21.1 (DEB 209 2017-03-23) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Mailman-Approved-At: Sat, 07 Aug 2021 14:21:51 -0400 Subject: Re: [Starlink] [Cake] [Make-wifi-fast] [Cerowrt-devel] Due Aug 2: Internet Quality workshop CFP for the internet architecture board X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Aug 2021 03:06:22 -0000 that matrix cannot create asymmetric paths (at least, not unless you are also tinkering with power settings on the nodes), and will have trouble making hidden transmitters (station A can hear station B and C but B and C cannot tell the other exists) as a node can hear that something is transmitting at much lower power levels than it cn decode the signal. David Lang On Mon, 2 Aug 2021, Bob McMahon wrote: > On Mon, Aug 2, 2021 at 4:16 PM David Lang wrote: > >> If you are going to setup a test environment for wifi, you need to include >> the >> ability to make a fe cases that only happen with RF, not with wired >> networks and >> are commonly overlooked >> >> 1. station A can hear station B and C but they cannot hear each other >> 2. station A can hear station B but station B cannot hear station A >> 3. station A can hear that station B is transmitting, but not with a >> strong >> enough signal to decode the signal (yes in theory you can work around >> interference, but in practice interference is still a real thing) >> >> David Lang >> >> > >