From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B09B53B2A3; Thu, 16 Feb 2017 04:16:48 -0500 (EST) Received: by mail-wm0-x236.google.com with SMTP id v186so61197277wmd.0; Thu, 16 Feb 2017 01:16:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kl4vn1/ToK9vja2jEgZqpbOpT8GSx5zaVBKgXpucrnA=; b=YhDBN6eWbDd+6VEhpkMCcxTc+GRhNEhcPV8RbJMBrlQW0tr3zeVhtCIc8HyRK0eKil +uKbT5+k804RbjteH9h9I05v1C7pqtdrPbybncreo2osKUyx0wZFcLeuSOxNJkcB1rDa odUJNcZ+ZHgZhX1VJ/ThQD6/mt7F5BkMLq+uR3sioLQitGa37a18lOvXr3NNE1qYAvGP QU6QmmE53WnQHNZrWAK8h+odqQ3LCiek/aHWkd6R4PUAlRwsUfBdlwC6MVCUFVESKgCT QoI0ON7PoWscx+sh+SqRlZQHVzIXnuytNkVBcCU+lDCu9cQW5yzlZOn93cWkv/2y3Czj l/wA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kl4vn1/ToK9vja2jEgZqpbOpT8GSx5zaVBKgXpucrnA=; b=UBarYN2NaIO2XsiX14nd6RdnBU6omkp7INVGg9081exXkMw2+Vx69ZQmb/Z6bZJME2 NhRhQnkXpzqdcvY4BF2LEc+PqgijYgfXuNAoK5pzfEh+YOFiqM0t+KYeRNDfQljMgW9J 0hp3fv4A6goMynn33W7ghP5aQceV8v3GRJ1Lwqsn3T2OFCw4YBT07NK2xxaHI+Jbal5p z3Ag96vq5YCgY64ZGtKmGyMCmUly9n+qp5LLrK9rc5x1Z/UtArkOqFcPLyWogUb2pEfS +Ei9iKXjscQayMaqDnwIaNzaJFeKIm7JPnNIGdlIKF/UbMXFpLg0QSKry560+g4uy0HS SnKQ== X-Gm-Message-State: AMke39nqE+J9XVTESZYyXi0CByFEMystp0Z3e5iwMo9XE+x+8qdjPxPivpEPJ5nhyuZIYw== X-Received: by 10.28.137.203 with SMTP id l194mr11565909wmd.63.1487236607740; Thu, 16 Feb 2017 01:16:47 -0800 (PST) Received: from [10.72.0.34] (h-1169.lbcfree.net. [185.99.119.68]) by smtp.gmail.com with ESMTPSA id u189sm2693078wmu.1.2017.02.16.01.16.46 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 16 Feb 2017 01:16:47 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Pete Heist In-Reply-To: Date: Thu, 16 Feb 2017 10:17:06 +0100 Cc: cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: References: <32C42951-373F-4D90-8936-AA07039E5D73@gmail.com> <877f5c2pew.fsf@toke.dk> <42AC44CD-8C22-4EBC-B6AB-7786BA505D07@gmail.com> <35E83BE1-73D8-4FF9-B2E8-A49073E67EBA@gmail.com> To: Sebastian Moeller X-Mailer: Apple Mail (2.3124) Subject: Re: [Make-wifi-fast] [Cake] Flent results for point-to-point Wi-Fi on LEDE/OM2P-HS available 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: Thu, 16 Feb 2017 09:16:48 -0000 > On Feb 16, 2017, at 9:42 AM, Sebastian Moeller = wrote: >=20 >> On Feb 16, 2017, at 08:57, Pete Heist wrote: >> [=E2=80=A6 discussion about DSCP to WMM classes mapping] >> This always makes me wonder what=E2=80=99s to keep someone from just = marking all their traffic 0x7 and stomping over everyone else. >=20 > I have a gut feeling that an AP in a untrusted/hostile = environment should monitor the usage of the 4 different WMM classes and = step up their class accordingly. That is in an environment where there = is a lot of AC_VO or AC_VI traffic the AP should elevate its normal data = packets priority to match as not too be drowned out by the other = senders. Sort of a reciprocal tit-for-tat approach, with the goal that = the AP will keep access to a decent share of airtime. But since I am a = layman in these matters, I might be out to lunch on this=E2=80=A6 At first I was thinking to just remove diffserv markings entirely, say = with Cake=E2=80=99s besteffort flag, but I think that =E2=80=9Cgood=E2=80=9D= and =E2=80=9Cotherwise unknowing=E2=80=9D users would suffer, which I = think in FreeNet is a vast majority of users. I think the challenge might be what metric to use to know when classes = are being abused. Maybe roughly if dscp_value * bytes_transferred = exceeds some threshold in some given period of time, that would work. = Best effort wouldn=E2=80=99t affect this metric so they can use this = class all they want, and if someone just uses their connection for = typical VoIP usage, the threshold shouldn=E2=80=99t be exceeded. Only = when a lot of data is transferred per period of time in higher classes = would they exceed the threshold. For now, we could just measure this (with iptables?) and send an admin = email when the threshold is exceeded, then automate a strategy to combat = it if needed. But I bet most users in a community WISP, if notified, = would just try to help fix the problem=E2=80=A6 :) Pete