Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp7967783ybn; Tue, 1 Oct 2019 00:43:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqy7R7BkDStg+M05eQ3UbavG/8jqxSYoX5CKb3JtPkrCi1LQYoDd0nhnOUg8SkbRENbIz6Hd X-Received: by 2002:a50:ab0f:: with SMTP id s15mr24008340edc.119.1569915799736; Tue, 01 Oct 2019 00:43:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569915799; cv=none; d=google.com; s=arc-20160816; b=hqslsQRQ5KXvNU4NuaToLO7MsORhlBeSsng2yBuJTvkUEZuu5nEQ0sfhMwn0uGr8oc Q/HPX2rT2ggSqFEgGE5uE4d8i8S5uKx7cOXfEEwydKBOqci4ihaGcwBgNdmZOltnON+q /gm7vzxSI6at3UkA8R5tJAJIJvjG23Pmgn8eygDEm8+BHvj0eyymX/IY8i1eeKCK6Kvb e4Sijm2jc5glpE0y3FGTa9n6+66udQyBtRGPsKwjm0rZtyWCR3+vmgMn3fvpZRaaMnKK E6GUOTG8crldYOqg/TzjBKeNTYecUVylQYYCysRk1nohm3Nv5kbgfb1lWR8rsda0mcrV i2+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=/NoUxUBkKLt9Eej5CyjOrxcm/wJkB3R2+gq45aNNdAc=; b=zg8VZA/izSY9XHGXPLWaA+Y/nOz9W1z2TsgH2g4eWltOgw5xY8kRf7osR/iCXeTTA5 EY1nw7OG3chZEs7U7HM6aqUoC3Az4NXts1jtku6udzYUSaDIPwmnNr95wj8O+OGQNSlf JpoNgj1ppuDZ3m+yeqCvDeDCvCK9hZv77YncxscHg/I+evqHH3Fi9C1XDPuCy6ZFeUvJ c2INU6d721y4XHFCiRpyk7sX2Fk96gEuWznLgfUMAopdC+rDuR1cZ2kzFVGXp7qYjrqf cgyVmoUlpA3/1N2kHOp1PMfCHHiL/ZJM/qFx5CdUhgtvPTbFydsrZ11AlFAwSAf93P3H 0VXg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q35si9359400eda.122.2019.10.01.00.42.54; Tue, 01 Oct 2019 00:43:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733080AbfJAHkA (ORCPT + 99 others); Tue, 1 Oct 2019 03:40:00 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:56050 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731358AbfJAHkA (ORCPT ); Tue, 1 Oct 2019 03:40:00 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.2) (envelope-from ) id 1iFClL-00014u-GN; Tue, 01 Oct 2019 09:39:59 +0200 Message-ID: Subject: Re: mac80211_hwsim (kernel 4.18+): wmediumd + 2.4Ghz From: Johannes Berg To: Ramon Fontes , Krishna Chaitanya Cc: linux-wireless Date: Tue, 01 Oct 2019 09:39:58 +0200 In-Reply-To: (sfid-20190930_202838_727383_A4E81EAE) References: <80d9c12986ec0a13c34672ca1c16f37cae0cc096.camel@sipsolutions.net> <39d646206446159a2b0a67ee7d8667483ade0733.camel@sipsolutions.net> (sfid-20190930_202838_727383_A4E81EAE) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Mon, 2019-09-30 at 15:28 -0300, Ramon Fontes wrote: > > Based on this info, looks like hostapd/wpa_s versions might be causing > > the difference, > > can you please confirm the versions on both? > > They have the same hostap (hostapd + wpa_s) version: > Hostapd v2.10-devel-hostap_2_9-102-g12de14907+ > wpa_supplicant v2.10-devel-hostap_2_9-102-g12de14907+ Do they also have the same version of wmediumd? > I've tested with v2.8-devel-hostap_2_7-313-g3e949655c+ too. > > In this short video (https://www.youtube.com/watch?v=f6rrHIGpePA - > running on VirtualBox) you can see the problem in action. Through this > video you can see that it works with 4.16 and 4.17, and doesn't work > with 4.19 (I forgot to repeat the test with 4.18, but I confirm that > it has the same behaviour as 4.19). Regardless, we should fix this stuff ... johannes