Received: by 2002:a05:7412:6592:b0:d7:7d3a:4fe2 with SMTP id m18csp2453049rdg; Mon, 14 Aug 2023 03:07:15 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEymkG4zJhbNo/YrdU3to8mUWdNiy3pfSuh36jvoTrtqocNHLnlMJ4VnfugaYoHudfDkzP2 X-Received: by 2002:a05:6a00:13a2:b0:668:69fa:f791 with SMTP id t34-20020a056a0013a200b0066869faf791mr11112030pfg.3.1692007635396; Mon, 14 Aug 2023 03:07:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1692007635; cv=none; d=google.com; s=arc-20160816; b=nfUUSfbZuKJk4mfamOD3jDv8M1meEkOjMZbZaef7it/RD3Pupg008goZikygz0PzZU IIXd+e3h5E5MMEuZz1t4Ak28OloGPUKHS9txkoBxBvQe933VTghVrhBa6GN6Dcdwnfoe 4bdpvIkDeJtbwUkrJMeJXxDvCNqpLxZlNItQwhGusCbNyfSTuhNpc7YOr1KHnTot8N+9 1q+cbxDGvg0laBXUCVDfcheqKkox3fbvMF5KG1nNSHalJ31S1A27wnMmXoXbhFBS5PMI ZfcUeZ3ArZZeBLigxTzG1xKRF87NJvlB/g4Mv1RlXlvXApMHPPwwSfo90hXlYlCXgOse 1yAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=i877FpT5qodl1tYCxsJp7SLUPoE/IQXdlXHatl2Wf8I=; fh=fbvD3jBbUYhP7llAG1oek4g5NNPD1QYvJxlqhBOd0yE=; b=vYCERiQutqhKfgJQyRolt4wd2cuZW0eisWewIN11YsT+nkoW+koLxRjJdcNf+iXGT7 0qbPaD2BM5yKSSv7VznilE9Q2YrNVuBa4fBKCDM8zJzyKlo4WoI3BbvE5v7HzhtAzFp6 aDsMzMHdu76HBTgXirs++Z2oJ9QsMY7zkS2cSpDEfFaNUkffaVS/SkwXZ2JYZIyhn3Bd 9Gp6WiyNOffbmgwnSsMQ7HPmXiNJcZ2g9oFSga/WVJ6HhnnIdmIcDMlrb+HPJnZqG3Cu yanmKxvDazguWZxoAY9NC4zvtHnaoYr9LG7qhend/uD5gIzOfMLRK2j9eIatUmd+x+S7 OKCg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=mZwExuPd; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l1-20020a056a0016c100b006874c2f0a36si8001872pfc.156.2023.08.14.03.07.05; Mon, 14 Aug 2023 03:07:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=mZwExuPd; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235456AbjHNJfY (ORCPT + 54 others); Mon, 14 Aug 2023 05:35:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49028 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235775AbjHNJAG (ORCPT ); Mon, 14 Aug 2023 05:00:06 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:242:246e::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B33472117 for ; Mon, 14 Aug 2023 01:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=i877FpT5qodl1tYCxsJp7SLUPoE/IQXdlXHatl2Wf8I=; t=1692003553; x=1693213153; b=mZwExuPdxJU9FUoOcxy9gTOBSyUZMaBox4kAsyXkM3KHYiX Y7UCoN9rZKMZ3Xt/k3B6+75P/6gK8A9Felt/pAK1HlztduhytbyW1On4IahgU/JkFQnI1QBNft4VV UX2AejZlL9xScbj5bc1eMp3VwVpwEG6RmSd9SHQmVpAsAOompLTFxnpspCGVYonZhsImnb7J5kAT8 ctu0EItJSnnAN/RwotQtnrs0N0tuxcoN2DgZN3jvjUXrx/wUjd/B/DeUVmwbInAv06lu26xlpipYw dp81sfKFYdhirA0SUhKetlxYKO/t5bPwqnAzXNQWT+oTEb5ALAmKePkJ9rMRu8zg==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1qVTPS-006ZAS-1b; Mon, 14 Aug 2023 10:58:46 +0200 Message-ID: Subject: Re: [PATCH] wifi: Add support for sending BSSMaxIdle in association request From: Johannes Berg To: Krishna Chaitanya Cc: linux-wireless@vger.kernel.org Date: Mon, 14 Aug 2023 10:58:45 +0200 In-Reply-To: References: <20230719194039.16179-1-Chaitanya.Tata@nordicsemi.no> <2307e1741e9d32e8f1ffc4e83c73b63a4e32512b.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 X-malware-bazaar: not-scanned X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED, SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Mon, 2023-08-14 at 01:56 +0530, Krishna Chaitanya wrote: > >=20 > > > Just remembered why I had to implement this in kernel, the associate/= connect > > > data structure in wpa_s `wpa_driver_associate_params` doesn't have an= y > > > ies/extra_ies, it only gives wpa_ie and rest all are parameters for m= ac80211 > > > to use. So, had just extended this as well, do you think we should ad= d > > > this ies/extra_ies > > > to the association like we do for scan? Or as MLME is in mac80211, > > > just use this patch as is? > >=20 > > Not sure I follow all that reasoning - is that something internal to > > wpa_supplicant? Fundamentally with my cfg/mac hat on I'm not sure I car= e > > so much about wpa_s internal data structures? > >=20 > > Things like extended capabilities are also added to the "extra IEs" by > > wpa_s, so surely this would work too? >=20 > I was only pointing out that AFAIK there is no mechanism to pass "ies" in > the associate command from userspace, except for WPA IE. Oh you're talking about the associate command? You never mentioned that, and in fact most of your patch is concerned with mac80211 ... Would it kill the implementation you have to add "extra elements" rather than all these individual settings? Does this thing affect the local firmware implementation? I guess in a sense it must? I don't know ... and I have no way of ever finding out! So again this is one of those things where we're never going to see an upstream driver using it, right? I'm getting really close to just giving up on that. Since Jouni is happy to add vendor commands for settings left and right in wpa_supplicant, I pretty much think this stuff has failed. We're littering the nl80211 API with things that don't really get used upstream, or like here, do get used but in a way that's (a) pretty useless since it doesn't do anything but add an element wpa_s could have added itself, and (b) looks like just a fig-leaf for this exact reason? Shouldn't something be configured here to the NIC too? NIC should support it, etc.? What's even the purpose of this in mac80211? johannes