From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 904D83B29E for ; Mon, 24 Oct 2022 19:05:47 -0400 (EDT) Received: by mail-wr1-x42e.google.com with SMTP id o4so10058804wrq.6 for ; Mon, 24 Oct 2022 16:05:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=YJOZ0GRxdfkjAUWOUVkLHFC783P2YZQh5IXynpXCZs4=; b=qmPCGHVxg7q5U1A5K86mXOD/UQYekmrSyGvAAzyo3Jk3qhYbqdkFAwL32MIC00mLw8 gw0gZIXYMHpM4AmkeGHIHtjA1+ymvFinF2F/EATGZbQ7UQ2G13YLmMWsKid7U5GNKtze XQ9bBsepezysscZ5wJyibfSivSmcrUNnbkmebNDxnP0761065zGn8NqDI5jD71iJexCx MseQ0pjhZGtdZSSCQshm65bcwKTj5KlVmVUCqSMUVBgDTW1nFlFI+dM6FlDr+SojOttg hd03M1xiOYdeAJqopIUzke2YJoQ0VT5OHD6olmEd6eDmpLrWHzRAxHMo7gCFr3r1uhR9 T5bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=YJOZ0GRxdfkjAUWOUVkLHFC783P2YZQh5IXynpXCZs4=; b=cXobDZUP0sHvSeoON2a8clS1iITniTvmjrIRhmJGLnVdpWiHpRx19cMYEr8KDWZPx1 6DbeMOfonA0SRq0sU+1bnEyvE+Easek4L7NN+mIPGG806voqh5bfKNIMQPqNtBVQ7hVw 7EO1Ln8fqMXXUUAgx7S3OVdRu2aMkY8B5rJBRqLcrpewoBbc4TIjvQHpQ2APmliW/M2n 3NLYVTmVDwPiGgkEwqE8/J5H4uu28nSsfRx0xE7Co4E2mpt/OGxX1riYJMvJqTMxMC5D Ifw07EWkxSR+JOdJanWcBWAIaNERIUwV5xzOTcMv7PLLobAsjGqjoXLPNhtEHdkWyngj Lf+Q== X-Gm-Message-State: ACrzQf3ExuffDJOxb6SIq+4MU7InRSQGkuS786kl0I9SVpK2b4vq7+wT X7CYtWXFyywUYyOkWCLaONW+HemFUWnWOBIJR2vjG5p4 X-Google-Smtp-Source: AMsMyM4vcsAFkFfGsm5xawZDLxpRvxGyYUZDRYvCowGLbfWTnkCb7v5Fabotg05FUrX31ESiDpNS7AFCeIPHeDmDbjY= X-Received: by 2002:a05:6000:69b:b0:22e:36aa:5f1 with SMTP id bo27-20020a056000069b00b0022e36aa05f1mr22610911wrb.430.1666652746334; Mon, 24 Oct 2022 16:05:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Taht Date: Mon, 24 Oct 2022 16:05:34 -0700 Message-ID: To: Herbert Wolverson Cc: libreqos@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [LibreQoS] Rain Fade (was Ack-filtering) X-BeenThere: libreqos@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Many ISPs need the kinds of quality shaping cake can do List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2022 23:05:47 -0000 On Mon, Oct 24, 2022 at 3:58 PM Herbert Wolverson w= rote: > > Hit the wrong reply button, that happens a lot when I try to type on my p= hone. > > I'm going to test tracking many more flows early in the morning. It shoul= d slightly increase ram usage, and have no ill effects. "Should" doesn't al= ways work out, hence testing! > > I meant "flooding" in the "oh crap, site underwater" sense. We'd need a b= oat to get to one tower right now! It doesn't currently have power, which I= suspect is related. re: flooding, yea, forgot about that kind. :) I hate to harp on it more than once a week, but we designed fq_codel first and foremost to cope with rain fade on the backhaul. Now that people just use it to enforce plans :( gathering statistics as to radio behaviors when it rains, and/or clearly identifying weather, when looking at historical data seems apt. How bad are y'all's gear doing with rain fade on various techs and bands? in 08, in nica, I'd go from a working 70 db 10 mile shot to nothin at 5ghz when it rained, and I just laughed at the people trying to deploy 60ghz - but times change. I see a vendor trying to ship 60 with *really good antennas* into the office market... big question to ask when so busy, please ignore me. > > Turned ack filter off, after some customers reported issues (others were = really happy). The unhappy campers were all on Cambium devices, with good s= ignal and modulations. Maybe Cambium is doing some "magic"? We'll try a uni= directional test tomorrow. Maybe an exceptions db for stuff that is too smart or weird. TCP "accellerator"s are everywhere. > > On Mon, Oct 24, 2022, 4:57 PM Dave Taht wrote: >> >> On Mon, Oct 24, 2022 at 2:19 PM Herbert Wolverson via LibreQoS >> wrote: >> > >> > Highly un-scientific (we need to let it run for a bit and do a proper = before-after comparison that includes a decent timeframe), but I like the q= uick'n'dirty results of testing "ack-filter": >> > >> > We've been having a Bad Network Day (TM), with sudden flooding making = us use some pretty constrained >> >> I've been looking at various ddos mitigation schemes of late. Are you us= ing any? >> >> >- so our latencies were really suffering in one region. That region jus= t happens to be the worst part of our network (we haven't finished digestin= g an acquisition; there's even Bullet M2 omnis up there!). Lots of relative= ly low-speed plans, all with big variance (10/3, 25/5, I found a 5/1 that s= omeone forgot to upgrade!). They seem to have benefitted greatly. The parts= of the network that were doing great - are still doing great, with very li= ttle change. >> >> I made my previous comments in looking at the swing downwards being so >> large, possibly not being a positive direction (my ever suspicious gut >> was reacting, but I wasn't qualifying the numbers - been a long day >> here too) >> >> I also forgot to mention that ack-filtering uses up less txops on >> older versions of wifi. Very useful. I'd meant >> to put it into my mt76 stuff ages ago but got overwhelmed by bugs. >> >> > Just a quick'n'dirty test. I'll try and put something more useful toge= ther tomorrow, when it's had a chance to see how peak time hits it. >> >> :crossed fingers: >> >> > >> > (Also, this digging revealed an issue with pping-cpumap in production.= It wasn't tracking enough flows, so the reporting is heavily biased toward= s the top-consumers - who are likely to be monitored before the buffer fill= s up and it stops counting until stats are read. So I added a "maximums.h" = file to make it easy to set user limits, and made flow-count derive from th= at.) >> >> I think polling it more frequently would be closer to the typical >> durations of flows. Most flows last for under 3 seconds. >> >> What would be the harm in vastly expanding the number of flows it tracks= ? >> >> /me hides >> >> > _______________________________________________ >> > LibreQoS mailing list >> > LibreQoS@lists.bufferbloat.net >> > https://lists.bufferbloat.net/listinfo/libreqos >> >> >> >> -- >> This song goes out to all the folk that thought Stadia would work: >> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-69813666= 65607352320-FXtz >> Dave T=C3=A4ht CEO, TekLibre, LLC --=20 This song goes out to all the folk that thought Stadia would work: https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-69813666656= 07352320-FXtz Dave T=C3=A4ht CEO, TekLibre, LLC