Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp5755603ybe; Tue, 17 Sep 2019 13:00:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqzLpCEvFgcWVYvBsQxgEkLbsFp6FUslxF5Fs90FsSSKDZB/vzcAK4ZPe4NFiJZqHFEwiEH/ X-Received: by 2002:a50:d6db:: with SMTP id l27mr6722609edj.164.1568750408459; Tue, 17 Sep 2019 13:00:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568750408; cv=none; d=google.com; s=arc-20160816; b=bO+HWMkE4sMXCEVcCmLtNjtsa6i/reKC3l4+dGpdTgE2sqhg9MsluW6u1PD5Bf4RQz 3NhNZs/+yUmxiLbBP1Q7xRavJwzZCaQ1aMbr/jc4h8buGB8O5KaOdXNuOlMvSdqk1Js3 S8OtVWKegw8wD5xac+NFo61qJ67r+7Zs2dvFzXXGnUuURNzNu6/Q5MpfoCygJfNjkUWv baoyZC5Elgoi2OBZ3b6hA/Z4jNtUjBTAx/RwiWBgDArdR0jUzk4OGdKh5dSWwMMUBEMa 6tY6/ZgakWhQlafEV/wRDBjuX8ERWBNtjhSG7yyxPkEKg3k0AJ0Iah9mPP7ZE9ewwVaJ wK1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=2eWB0lu+YjYLmf0tkBB5Li6UOQDXJcb8ARu8VnJrd4s=; b=WR4P+xlV/4mMw+ftrxmD2+lNOX7GrfD0owLw+tY1ByXj8YmaJ40vLnHziLExfxuhwF tb1+HMCzj3plCNvSGQiMWvHhc+lUN90xRM7jNo8TvoxxEoIWfceTRhWiElSrUu4/Vhs3 OJZwDHhtyulBFlBzceOYBJxuXA5MhCMxWKmMxRHP2AWom9cDLUD8+04f8SePlvHKVTp7 EoDn8EldRrj2/HmgYy6dy9c2tYxSmXyxQ07Bpt2U0QBV1nrJzsb7+NAe6jV1Jcp0T8kw rfHn6bFKWFDD1pWg1wew0jeXeXJwLTtTiKyR/NX6g75NXgH3D7ON/Bvb8+8I4dX+uEnu 0Kjg== 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 ca9si1897210edb.79.2019.09.17.12.59.42; Tue, 17 Sep 2019 13:00:08 -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 S1729837AbfIQTHW convert rfc822-to-8bit (ORCPT + 99 others); Tue, 17 Sep 2019 15:07:22 -0400 Received: from coyote.holtmann.net ([212.227.132.17]:42899 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726523AbfIQTHW (ORCPT ); Tue, 17 Sep 2019 15:07:22 -0400 Received: from marcel-macbook.fritz.box (p4FEFC197.dip0.t-ipconnect.de [79.239.193.151]) by mail.holtmann.org (Postfix) with ESMTPSA id 64923CECC3; Tue, 17 Sep 2019 21:16:11 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [RFC 0/4] Allow live MAC address change From: Marcel Holtmann In-Reply-To: <20190917204419.41235404@smicro.local.lan> Date: Tue, 17 Sep 2019 21:05:51 +0200 Cc: linux-wireless@vger.kernel.org Content-Transfer-Encoding: 8BIT Message-Id: References: <20190904191155.28056-1-prestwoj@gmail.com> <4c43ea6a74cacc61184bc5b1387fecaa40711369.camel@gmail.com> <4909a428ee6fef2bf8b0e61841bc88062f534b13.camel@sipsolutions.net> <896183390a396e8e0508622eceb3664effcb3c30.camel@gmail.com> <87a7b8lciz.fsf@tynnyri.adurom.net> <844f1a1dc72ec73df5a86864b410bbc490c4abdd.camel@gmail.com> <87imprbc0j.fsf@kamboji.qca.qualcomm.com> <763f4560-ba78-b0e7-6855-fd4bc048ec13@gmail.com> <20190917204419.41235404@smicro.local.lan> To: Bob Marcan X-Mailer: Apple Mail (2.3445.104.11) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi Bob, >>> For user experience scanning and DHCP are also important, what kind of > numbers you get when those are included? No need to have anything> precise, I would like just to get an understanding where we are> nowadays. >> >> Scanning heavily depends on the RF environment and the hardware. In our testing ath9k takes stupid long to scan for example. >> >> But in a sort of best case scenario, using limited scan and no mac change, iwd connects in ~300ms. People have reported that they have not finished opening their laptop screen and they're connected, so at that level of latency, every millisecond is important and totally worth fighting for. Randomizing the MAC would penalize our connection times by 2X (300 ms at least). And Android folks have reported the penalty to be as high as 3 seconds. So this needs to be fixed. And do note that this is a feature every modern OS implements by default. > > Randomizing the MAC is a stupid decision. > Do you realy expect that this will add something to the security? the mac randomization is about privacy. Regards Marcel